[Top][All Lists]

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

Re: Problem with AC_CONFIG_FILES targets that contain variables

From: Ralf Wildenhues
Subject: Re: Problem with AC_CONFIG_FILES targets that contain variables
Date: Fri, 22 Aug 2008 10:42:58 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Hello Sander,

please don't top-post, thank you.

* Sander Niemeijer wrote on Fri, Aug 22, 2008 at 10:35:19AM CEST:
> Currently the part that may be misleading is the part where it says that 
> one is encouraged to avoid using 'AC_CONFIG_FOOS([$my_foos])'. This 
> phrasing of the sentence suggests that it may still be valid to do so.
> In fact, it is not. Running configure works. But, just as my example, a 
> config.status on either fooo or foooo does not. Even adding an  
> initialisation of my_foos to init-cmds wont help. I would have guessed  
> that maybe running "config.status 'fooo foooo'" would then still have  
> worked, but even that doesn't seem to (config.status apparently splits  
> up all command line arguments, even if they were quoted, so it gives an 
> 'error: invalid argument: fooo'.).

Erm, we fixed a regression that occurred in 2.62 in this area recently.
Can you be more specific and show the test case that fails?  I'd like to
make sure 2.63 does what the manual promises.

Which Autoconf version did you use?

> I would rephrase the section to explicitly forbid users to use the  
> my_foos construct as is currently mentioned and generally advise users  
> not to use variables in the tag section. It would be good to mention  
> what users can expect if they would still try to do it (i.e. configure  
> works, but config.status wont).

Only if we can't get it fixed.


reply via email to

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