, December 27, 2004 2:56 PM
To: wolfgang haefelinger
Cc: autoconf@gnu.org
Subject: Re: CONFIG_FILES
Hello,
you described the following problem with autoconf-generated config.status:
On Wed, Dec 22, 2004 at 10:34:36PM +0100, wolfgang haefelinger wrote:
> autoconf manual states in 15.1 t
t; instantiate [..] Before, environment variables had to be used.
>
> Perhaps a known problem but the new approach is not identical to
> the old one.
>
> This works well:
>
> $ CONFIG_FILES=./Makefile config.status
> config.status: creating ./Makefile
>
> But this fai
Greetings,
autoconf manual states in 15.1 that
>> `config.status' now supports arguments to specify the files to
>> instantiate [..] Before, environment variables had to be used.
Perhaps a known problem but the new approach is not identical to
the old one.
This works well:
> "David" == David Morgan <[EMAIL PROTECTED]> writes:
David> Akim, It is unchanged at this time.
Actually Autoconf was changed, but its ./configure was not.
David> I can wait till tomorrow.
Good morning! :)
Akim,
It is unchanged at this time.
I can wait till tomorrow.
[EMAIL PROTECTED] wrote:
>
> On Wed, Nov 29, 2000 at 11:00:31AM -0800, David Morgan wrote:
> > Hi guys,
>
> Hi from home :)
>
> > The config_files problem is not:
>
> Sorry, I fixed that one
On Wed, Nov 29, 2000 at 11:00:31AM -0800, David Morgan wrote:
> Hi guys,
Hi from home :)
> The config_files problem is not:
Sorry, I fixed that one later, it should be fixed now. I forgot there
was this one pending when I first sent you the message. Sorry.
Hi guys,
Well we are getting to a different place than what we were before.
I seems the sed/expr problems are better.
The config_files problem is not:
In config.status we have the lines generated (166-168):
if $ac_need_defaults; then
: ${CONFIG_FILES=$config_files}
fi
This is not portable
