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=libburn&arch=ppc64el&ver=1.3.2-1&stamp=1408406204
https://buildd.debian.org/status/fetch.php?pkg=libburn&arch=i386&ver=1.3.2-1&stamp=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
