[libtool] unpackaged documentation makes autoconf runs fail

Bug Reports
#1

REPRODUCIBILITY: 100% (always)
OSVERSION: 4.4.0.72 , 4.5.0.21
HARDWARE: Sony Xperia 10 III - xqbt52 - xqbt52 - 1.0.0.176 - aarch64
UI LANGUAGE: English (UK) (user: en_GB, os: en_GB.utf8)
REGRESSION: not specified

DESCRIPTION:

The current packaging of libtool moves some files where actual runs of libtoolize do not find them:

See https://github.com/sailfishos/libtool/blob/master/libtool.spec#L105

This results in the files ending up here:

/usr/share/doc/libtool-2.4.6/README
/usr/share/doc/libtool-2.4.6/libltdl/README
/usr/share/licenses/libtool-ltdl-2.4.6/COPYING.LIB

But libtoolize expects them at:

 /usr/share/libtool/README
 /usr/share/libtool/COPYING.LIB

PRECONDITIONS:

none really

STEPS TO REPRODUCE:

  1. clone an autotools-based source tree
  2. install libtool-doc, libtool-ltdl-devel
  3. run autoreconf -fiv
  4. libtoolize fails

One example where this fails is graphviz: graphviz / graphviz · GitLab

EXPECTED RESULTS:

autotools and friends running successfully

ACTUAL RESULTS:

[   24s] libtoolize: putting libltdl files in LT_CONFIG_LTDL_DIR, 'libltdl'.
[   24s] libtoolize:   error: '/usr/share/libtool/COPYING.LIB' not found
[   24s] libtoolize: creating file 'libltdl/Makefile.am'
[   24s] libtoolize:   error: '/usr/share/libtool/README' not found
[   24s] libtoolize: creating file 'libltdl/configure.ac'
[   24s] libtoolize: copying file 'libltdl/aclocal.m4'
[   24s] libtoolize: creating file 'libltdl/Makefile.in'
[   24s] libtoolize: copying file 'libltdl/aclocal.m4'
[   24s] libtoolize: creating file 'libltdl/Makefile.in'
[   24s] libtoolize: copying file 'libltdl/config-h.in'
[   24s] libtoolize: creating file 'libltdl/configure'

MODIFICATIONS:

not applicable

ADDITIONAL INFORMATION:

the initial version of this bug report was created using Bugger 0.9.10+git1
1 Like
Community meeting on IRC 28th September 2023
#2

Quite interesting that no other packages have had issues like this, the files have been in the same location for years already. I will have a look at other builds which use libtool. As for this specific package I would personally use the cmake build system also supported by graphviz.

2 Likes
#3

I was surprised as well. Maybe it’s specific to how graphviz wants to do things, I don’t know enough about these tools to be able to tell.

It’s a pity as the pre-'configure’d src tarball works fine, but I wanted to move to tar_git.

Thanks for the hint, I will try that.

Sometimes cmake is another can of worms, with some sfos packages not shipping cmake modules and/or cmakelists not falling back to pkgconfig.