On 10/08/2012 10:49 PM, Paul Wise wrote: > On Mon, 2012-10-08 at 22:03 -0600, Eric Blake wrote: > >> I still prefer the idea of being able to set an environment variable, >> $CONFIG_GUESS, rather than going hunting ourselves. Then, porting to a >> new config.guess script is a matter of calling: >> >> ./configure CONFIG_GUESS=/path/to/new/version >> >> rather than hoping that a hard-coded hunt will find the new config.guess >> appropriate for the system wanting the upgrade path. > > Changing the command-line to ./configure doesn't scale. Exporting an > environment variable possibly sounds like an approach some folks would > need, Then call: CONFIG_GUESS=/path/to/new/version ./configure and make CONFIG_GUESS a precious variable within configure. > so I have added it in the attached patch. For Debian it would be > easiest to just install the autotools-dev package in build chroots > (config.guess and config.sub are placed in /usr/share/misc) since it > doesn't require fiddling about with configuration files for build daemon > software, which usually doesn't leak random environment variables into > the build process. I still stand by my opinion that an env-var is sufficient, and we do not need a path walk. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
