Hi Helmut, On Mon, 02 Jan 2017, Helmut Grohne wrote: > while working on #843073, we agreed to merge Raphaël's patch on the > provision that we would revert it if it causes breakage. Unfortunately, > that actually happened. It breaks build cross compilers (stage3): > > https://jenkins.debian.net/job/rebootstrap_musl-linux-mipsel_gcc6/19/console > | DIRNAME= DEB_HOST_ARCH=musl-linux-mipsel ARCH=musl-linux-mipsel > MAKEFLAGS="CC=something" dh_shlibdeps -plibgcc1 > -l/lib/mipsel-linux-musl:/usr/lib/mipsel-linux-musl:/lib/mipsel-linux-musl:/usr/lib/mipsel-linux-musl > | dpkg-shlibdeps -Tdebian/libgcc1.substvars -l/lib/mipsel-linux-musl > -l/usr/lib/mipsel-linux-musl -l/lib/mipsel-linux-musl > -l/usr/lib/mipsel-linux-musl > debian/libgcc1/lib/mipsel-linux-musl/libgcc_s.so.1 > | objdump: /usr/lib/x86_64-linux-gnu/libc.so: File format not recognized > | dpkg-shlibdeps: error: objdump gave error exit status 1
Can't you just install "binutils-multiarch" when you build such cross compilers? That would let us use objdump to inspect any library and let dpkg-shlibdeps figure out whether it's a library of the correct architecture or not. > Thus I am asking to do what we agreed upon: > git revert a927295c93fb7a17742441aa863aaffcf4a351b5 Please consider the suggestion above before going down that route. We could also make the error non-fatal and ignore .so files that objdump can't parse. But I would prefer using binutils-multiarch because it would be bad to ignore failures that mean something else than "file format not recognized". Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
