Bug#761761: ladr: libtool split: package needs a b-d on libtool-bin (or avoid using the libtool binary)
Package: src:ladr
Version: 0.0.200911a-2
Severity: wishlist
User: debian-cross@lists.debian.org
Usertags: libtool-split
As part of the effort to cross-build the archive, the libtool package
needs a split into an architecture independent part and an
architecture dpendent part (the latter only consisting of the libtool
binary). The split is already done for jessie/sid, but to enable the
cross buildability, the dependency in libtool on libtool-bin needs to
be removed, and libtool-bin needs to depend on libtool instead.
The vast majority of packages using libtool via automake don't need
the libtool binary, and thus no changes in the build dependencies, however
about 60 source packages are using libtool directly, and need changes.
- some packages just check for the libtool binary, and then don't
use it for the build (but are using libtoolize instead). Such
usages are seen in a script called buildcheck.sh, and sometimes
in autogen.sh scripts. The solution for these cases is to patch
these scripts to check for libtoolize instead of libtool, and
not to introduce the new build dependency.
- other packages just need the additional build dependency on
libtool-bin.
To test your packages with the libtool-bin package removed, please use
the binaries found at
deb https://people.debian.org/~doko/tmp/20140820 ./
It is not clear, if all of these changes can be done in time for
the jessie release, but it would be nice to have to be able to
cross-build more packages in jessie.
For questions and help please email the debian-cross ML.
For additional pointers please see
https://lists.debian.org/debian-devel-announce/2014/08/msg00013.html
and some discussion in the orignal issue filed for libtool (#682045).
The full build log can be found at:
http://people.debian.org/~doko/logs/20140912/failed-libtool/ladr_0.0.200911a-2_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
[...]
User Environment
â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??
HOME=/sbuild-nonexistent
LOGNAME=user
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable-amd64-sbuild
SCHROOT_CHROOT_NAME=unstable-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1000
SCHROOT_GROUP=user
SCHROOT_SESSION_ID=unstable-amd64-sbuild-e540d3e5-ac61-49bb-bc01-015a02b18c09
SCHROOT_UID=1000
SCHROOT_USER=user
SHELL=/bin/sh
USER=user
dpkg-buildpackage
â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??â??
dpkg-buildpackage: source package ladr
dpkg-buildpackage: source version 0.0.200911a-2
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Frank Lichtenheld <djpig@debian.org>
dpkg-source --before-build ladr-0.0.200911a
dpkg-buildpackage: host architecture amd64
fakeroot debian/rules clean
dh clean
dh_testdir
dh_auto_clean
make[1]: Entering directory '/«PKGBUILDDIR»'
make clean
make[2]: Entering directory '/«PKGBUILDDIR»'
cd ladr && make realclean
make[3]: Entering directory '/«PKGBUILDDIR»/ladr'
libtool --mode=clean /bin/rm -f *.lo *.la
/bin/sh: 1: libtool: not found
Makefile:56: recipe for target 'realclean' failed
make[3]: *** [realclean] Error 127
make[3]: Leaving directory '/«PKGBUILDDIR»/ladr'
make[2]: *** [clean] Error 2
Makefile:40: recipe for target 'clean' failed
make[2]: Leaving directory '/«PKGBUILDDIR»'
make[1]: *** [realclean] Error 2
dh_auto_clean: make -j1 realclean returned exit code 2
Makefile:46: recipe for target 'realclean' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [clean] Error 2
debian/rules:8: recipe for target 'clean' failed
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
Reply to: