> "Guido" == Guido Draheim <[EMAIL PROTECTED]> writes:
Guido> Akim Demaille wrote:
>> See AC_ARG_VAR.
Guido> taken. ... then again, AC_CACHE_CHECK does not use
Guido> it
I don't understand what you mean. I agree some high level macros such
as AC_CHECK_PROGS should document their first
Akim Demaille wrote:
> See AC_ARG_VAR.
taken. ... then again, AC_CACHE_CHECK does not use it wouldn't that be okay?
Just again, what about a second-level options that go in another helpscreen, and,
well, in that respect, I do support your position to the point that the
current helpscreen is al
> "Guido" == Guido Draheim <[EMAIL PROTECTED]> writes:
Guido> As the discussion does now lead a bit elsewhere, what about
Guido> second-level options, settable via VAR=VAL (or sth. alike)?
Guido> There was the discussion that for cross-compiling, people do
Guido> often have the needs to pres
Richard Stallman wrote:
>
> The most
> important example is when `configure' is re-run (which is not that
> uncommon; re-running `./config.status --recheck' when configure.in
> changes is becoming more and more common): any such variables set in
> the command line are lost i
