Hi Matthia and Chris, On Sun, Feb 17, 2019 at 11:18:00PM +0100, Chris Lamb wrote: > > For the advantage of everybody, here are links to the cross-builds from > > amd64 to mips64el and arm64 of procmail.
Thank you. > Wow, thanks for this! I had spent an hour trying to follow the > instructions on the Debian Wiki to get a crossbuild environment > which failed in a very strage way, so had shelved this for the time > being... It would help if you could share your frustration in more detail such that we can fix that. The whole idea that you'd need a "cross build environment" seems flawed though. What you need is a "build environment" and that happens to be a "cross build environment" automatically. If you decide to put that into words, [email protected] is a good place. > Anyway, with these: > > $ dget > https://volatile.mapreri.org/2019-02-17/130da1c8cbfd405daeb1a7d0a51f536d/ > procmail_3.22-26_mips64el.changes > […] > > $ ar x *.deb > > $ tar xfJ data.tar.xz > > $ find | grep bin/lockfile > ./usr/bin/lockfile > > $ file ./usr/bin/lockfile > ./usr/bin/lockfile: ELF 64-bit LSB pie executable, x86-64, version 1 > (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for > GNU/Linux 3.2.0, BuildID[sha1]=61490d858790e4dc01926e63843ad0509abd0371, > stripped > > $ ./usr/bin/lockfile -v > lockfile v3.23pre 2001/09/13 > Copyright (c) 1990-2001, Stephen R. van den Berg <[email protected]> > Copyright (c) 1997-2001, Philip A. Guenther > <[email protected]> > > > Perhaps I'm missing something, but this looks like /usr/bin/ > lockfile is ann amd64 binary, not a a mips64el one. What you are observing exactly matches my report thus far. procmail successfully cross builds binary packages that contain native binaries (for all architectures). Doing so is broken of course and we want lintian to flag such builds. Indeed, lintian has a tag for such behaviour for a long time: binary-from-other-architecture. The particular issue in this report is that the tag is not emitted for the procmail package when built for mips64el even though it should. I mentioned the arm64 build as a positive example: The package is also broken and lintian successfully flags it with binary-from-other-architecture. Thank you for looking into this Helmut
