Bug#753421: blocking the ppc64el architecture bootstrap
Hi,
On Wed, Aug 27, 2014 at 05:25:45PM +0200, Thomas Schmitt wrote:
Hi,
i am still riddling how to recognize an autotools version
which suffices for ppc64el.
Would it be possible to get to see such a regenerated
./configure from ppc64el ?
The way to know that is to look if you have the following lines in
configure:
powerpc64le-*)
LD=${LD-ld} -m elf32lppclinux
;;
powerpc64-*)
LD=${LD-ld} -m elf32ppclinux
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753421: blocking the ppc64el architecture bootstrap
Hi, i am still riddling how to recognize an autotools version which suffices for ppc64el. Would it be possible to get to see such a regenerated ./configure from ppc64el ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753421: blocking the ppc64el architecture bootstrap
Hi, Aurelien Jarno wrote: From the upstream point of view, you might want to release the next version with the autoconf related files regenerated with a relatively recent version of autoconf, automake and libtool. That's not without problems on my workstation. I will look whether i can upgrade. (The first question is what autotools version would be sufficient.) Whatever, the change is needed not only with libburn, but also with libisofs and libisoburn. libisofs fails on ppc64el with the same symptoms as libburn. libisoburn is not attempted because it needs the other two libraries. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753421: blocking the ppc64el architecture bootstrap
Hi, i am the upstream programmer. Don't hesitate to ask questions if you need help to fix this bug. Can it be that the linker of that ppc64el installation is insufficient ? I diffed the build logs of ppc64el and i386. These are suspicious: checking whether the gcc linker (/usr/bin/ld -m elf64ppc) supports shared libr aries... no --- checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes [...] checking if libtool supports shared libraries... no checking whether to build shared libraries... no --- checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes The source compilation part of both shows the same warnings and no errors. ppc64el finally fails with dh_install -a dh_install: libburn4 missing files (debian/tmp/usr/lib/libburn.so.4*), aborting make: *** [binary-arch] Error 2 Well, if the linker cannot create .so libraries, then this is no wonder. The logs i compared are: https://buildd.debian.org/status/fetch.php?pkg=libburnarch=ppc64elver=1.3.2-1stamp=1408406204 https://buildd.debian.org/status/fetch.php?pkg=libburnarch=i386ver=1.3.2-1stamp=1378654298 -- PS: If Debian decides to upgrade libburnia to 1.3.8, please consider to include a patch for libisofs because of http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/revision/1162/libisofs/fs_image.c Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753421: blocking the ppc64el architecture bootstrap
On Mon, Aug 25, 2014 at 08:23:20AM +0200, Thomas Schmitt wrote: Hi, Hi, i am the upstream programmer. Don't hesitate to ask questions if you need help to fix this bug. Can it be that the linker of that ppc64el installation is insufficient ? I diffed the build logs of ppc64el and i386. These are suspicious: checking whether the gcc linker (/usr/bin/ld -m elf64ppc) supports shared libr aries... no --- checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes [...] checking if libtool supports shared libraries... no checking whether to build shared libraries... no --- checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes This is indeed the issue. The libtool part of the configure script included in libburn is to old, and doesn't have the code to correctly detect the ppc64el. This causes the shared libraries to not be built. This is why a patch is provided in the bug report to regenerate autoconf related files at build time. From the upstream point of view, you might want to release the next version with the autoconf related files regenerated with a relatively recent version of autoconf, automake and libtool. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753421: blocking the ppc64el architecture bootstrap
Dear maintainer, The ppc64el architecture has been added to the Debian archive. Your package libburn fails to build as reported in bug #753421 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. Thanks, Aurelien [1] https://buildd.debian.org/status/logs.php?pkg=libburnarch=ppc64el -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
