* Sander Niemeijer wrote on Fri, Aug 22, 2008 at 01:12:42PM CEST: > > AC_INIT(foo, 1.0) > my_foos="fooo foooo" > AC_CONFIG_FILES([$my_foos], [], [my_foos='$my_foos']) > AC_OUTPUT > --- > > After running configure, try running either: > $ ./config.status fooo > or > $ ./config.status 'fooo foooo' > > Both will fail with: > --- > config.status: error: invalid argument: fooo
Ah, ok. Thanks for providing the explicit example, I seem to always stumble over mental parse errors when reading prose. Your example does not work with current git Autoconf. It is, however, not a recent regression either: 2.59 had problems with this already. >>> 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. > > This was assuming you would follow what you said: 'I don't think we will > fix this' Ahh, hmm, I consider the above as separate from the first issue we discussed (which *was* work-around-able). Still pondering whether to give up and document the limitation (that with the above, './config.status FILE' simply does not work), or to venture for a fix. Cheers, Ralf
