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

[Matthias Klose]

Package: src:cvector
Version: 1.0.3.1-1
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/cvector_1.0.3.1-1_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
	
[...]
   libtool --mode=link gcc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2  -Wall -ansi -pedantic -static -I /usr/include -Wl,-z,relro
 
 Before installing the CVector library and example programs, check
 that the install directory and install commands are correct:
 
 The current values are :
 
   /usr 
   libtool --mode=install cp 
    
 
 To compile the CVector library and example programs type:
 
   make clean
   make all
 
 To run a set of tests type:
 
   make tests
 
 To clean up the directories type:
 
   make clean
 
 To install the library and binaries type:
 
   make install
 
***************************************************************
 
make[1]: Leaving directory '/«PKGBUILDDIR»'
   dh_auto_test
 fakeroot debian/rules binary
dh  binary
   dh_testroot
   dh_prep
   dh_installdirs
   dh_auto_install
make[1]: Entering directory '/«PKGBUILDDIR»'
mkdir ./lib
mkdir ./bin
libtool --mode=compile gcc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2  -Wall -ansi -pedantic -I.  -c -c ./CVector.c
make[1]: libtool: Command not found
Makefile:237: recipe for target 'lib/libCVector.la' failed
make[1]: *** [lib/libCVector.la] Error 127
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_install: make -j1 install DESTDIR=/«PKGBUILDDIR»/debian/tmp AM_UPDATE_INFO_DIR=no returned exit code 2
make: *** [binary] Error 2
debian/rules:10: recipe for target 'binary' failed
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2