Bug#761784: python-cpl: libtool split: package needs a b-d on libtool-bin (or avoid using the libtool binary)

Matthias Klose doko at debian.org
Mon Sep 15 23:42:14 UTC 2014


Package: src:python-cpl
Version: 0.6.2-2
Severity: wishlist
User: debian-cross at 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/python-cpl_0.6.2-2_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
	
[...]
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-2.7' does not exist -- can't clean it
   dh_clean
 dpkg-source -b python-cpl-0.6.2
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building python-cpl using existing ./python-cpl_0.6.2.orig-test.tar.gz ./python-cpl_0.6.2.orig.tar.gz
dpkg-source: warning: ignoring deletion of file cpl/version.py, use --include-removal to override
dpkg-source: info: building python-cpl in python-cpl_0.6.2-2.debian.tar.xz
dpkg-source: info: building python-cpl in python-cpl_0.6.2-2.dsc
 debian/rules build
dh build --with python2
   dh_testdir
   dh_auto_configure
   dh_auto_build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/cpl
copying cpl/version.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/recipe.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/result.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/param.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/esorex.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/__init__.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/logger.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/dfs.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/md5sum.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/run.py -> build/lib.linux-x86_64-2.7/cpl
copying cpl/frames.py -> build/lib.linux-x86_64-2.7/cpl
running build_ext
building 'cpl.CPL_recipe' extension
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/cpl
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c cpl/CPL_recipe.c -o build/temp.linux-x86_64-2.7/cpl/CPL_recipe.o
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c cpl/CPL_library.c -o build/temp.linux-x86_64-2.7/cpl/CPL_library.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-2.7/cpl/CPL_recipe.o build/temp.linux-x86_64-2.7/cpl/CPL_library.o -o build/lib.linux-x86_64-2.7/cpl/CPL_recipe.so
   debian/rules override_dh_auto_test
make[1]: Entering directory '/«PKGBUILDDIR»'
(cd test/iiinstrumentp && ./bootstrap && ./configure && make CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE=500")
bootstrap: Checking for maintainer tools...
bootstrap: GNU autoconf 2.69 found.
bootstrap: GNU automake 1.14.1 found.
bootstrap: Error: GNU libtool not found in your PATH!
bootstrap: Error: You need libtool 1.5 or newer installed.
make[1]: *** [build_test_recipe] Error 1
debian/rules:7: recipe for target 'build_test_recipe' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2



More information about the debian-science-maintainers mailing list