autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bo


From: Eric Blake
Subject: Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
Date: Tue, 09 Oct 2012 06:05:18 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1

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   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]