* Arnd Bergmann <arnd@arndb.de> [030705 17:14]: > No, that's exactly the wrong way around. dpkg-libinfo (at least the > current proposal) uses dpkg-architecture to find the target > architecture and dpkg-architecture in turn calls gcc to get that. > It makes sense this way, although dpkg-libinfo might also call gcc > directy. Actually, my proposal dealt with what gcc cannot tell dpkg-architecture (at least not using gcc --print-libgcc-file-name), but... > There is a patch for gcc so that it calls uname(2) to find out if it > should build 32 or 64 bit binaries. Yes, that would be much better. Do you know where this patch lives? > You can then use the personality system call when you want to change > to building 32 bit packages, e.g. 'do32bit fakeroot > dpkg-buildpackage' (I don't know if there is already a tool that > changes the personality, but do32bit is probably not the best name for > such a tool). Works for me. Thanks. Bart. -- WebSig: http://www.jukie.net/~bart/sig/
Attachment:
pgpBU1Qzjg22K.pgp
Description: PGP signature