Your message dated Wed, 15 Oct 2014 13:55:03 +0200
with message-id <543e6097.7010...@debian.org>
and subject line fixed in NMU
has caused the Debian Bug report #761783,
regarding oss4: libtool split: package needs a b-d on libtool-bin (or avoid
using the libtool binary)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
761783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oss4
Version: 4.2-build2007-2.1
Severity: wishlist
User: debian-cr...@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/oss4_4.2-build2007-2.1_unstable_jdk-libtool.log
The last lines of the build log are at the end of this report.
[...]
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_midiloop
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_midimix
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_sblive
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_sbpci
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_sbxfi
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_solo
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_trident
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_usb
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_userdev
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_via823x
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_via97
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build/kernel/drv/oss_ymf7xx
/«PKGBUILDDIR»/build-tree/oss-build
/«PKGBUILDDIR»/build-tree/oss-build
find build-tree/modules/oss4 -type f -exec chmod -x {} \;
touch stamp-source-oss4
sed -e 's#_VERSION_#4.2-build2007#' < debian/oss4-dkms.install.in >
debian/oss4-dkms.install
sed -e 's#_VERSION_#4.2-build2007#' < debian/oss4-dkms.dkms.in >
debian/oss4-dkms.dkms
rm -rf build-tree/modules/oss4/debian
mkdir -p build-tree/modules/oss4/debian
cp -r debian/m-a/* build-tree/modules/oss4/debian/
cp debian/copyright build-tree/modules/oss4/debian/
cp debian/changelog build-tree/modules/oss4/debian/
chmod 755 build-tree/modules/oss4/debian/rules
cd build-tree/ && tar cjf oss4.tar.bz2 modules/
cd /«PKGBUILDDIR»/build-tree/oss-build/lib/libOSSlib && CFLAGS="$CFLAGS
-isystem /«PKGBUILDDIR»/debian/include-alsa" make libOSSlib.so
make[1]: Entering directory
'/«PKGBUILDDIR»/build-tree/oss-build/lib/libOSSlib'
make[1]: 'libOSSlib.so' is up to date.
make[1]: Leaving directory '/«PKGBUILDDIR»/build-tree/oss-build/lib/libOSSlib'
cd /«PKGBUILDDIR»/build-tree/oss-build/lib/libsalsa && CFLAGS="$CFLAGS
-isystem /«PKGBUILDDIR»/debian/include-alsa" make
make[1]: Entering directory '/«PKGBUILDDIR»/build-tree/oss-build/lib/libsalsa'
libtool --tag=CC --mode=compile cc -isystem
/«PKGBUILDDIR»/debian/include-alsa -I../../include -I../libOSSlib -c main.c
make[1]: libtool: Command not found
Makefile:13: recipe for target 'main.lo' failed
make[1]: *** [main.lo] Error 127
make[1]: Leaving directory '/«PKGBUILDDIR»/build-tree/oss-build/lib/libsalsa'
make: *** [stamp-build-libsalsa] Error 2
debian/rules:45: recipe for target 'stamp-build-libsalsa' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 4.2-build2007-2.2
fixed in 4.2-build2007-2.2
--- End Message ---