On Fri, Feb 01, 2002 at 12:09:15PM -0200, Henrique de Moraes Holschuh wrote: > 0. dpkg-buildpackage has already run dpkg-architecture and set those > variables for you anyway, one might as well use them for something like > Debian policy urges one to. > 1. The build and host architecture are correctly set to the ones Debian > should be using (e.g. i386-pc-linux-gnu for all ia32 machines). And > anyone who wants to set it to something else just needs to set the proper > environment variable. > 2. config.guess is never called (a damn Good Thing) > Less wasted CPU cycles, and one less point of failure are a Good Thing! > One needs only to look at how the newer 2.4 kernels broke config.guess > on MIPS to understand why (btw, have you updated your config.* crap this > year? if not, you have the broken MIPS code in your package). > 3. It looks like the Right Way to do things re. the > almost-never-used-for-anything build and host stuff in GNU config, > and the spirit of section 5.2 and 12.1 of Debian policy. 4. It's necessary for cross-building any package that uses autoconf. While there are many issues with cross-building, there's no reason that cross-builds of Debian packages should be more difficult than cross-builds of upstream sources. > The question is: > Should I try to get the above way of calling configure to be the "do it > unless you know damn well you need to do it differently" way of doing things > in all Debian packages that use GNU autoconf? I believe so, but of course I think you know that already based on the bug I filed against dh-make. :) Steve Langasek postmodern programmer
Attachment:
pgp7LoWzYDb0l.pgp
Description: PGP signature