RE: How to cache $CFLAGS, $LIBS etc.

["Andrej Borsenkow" <Andrej.Borsenkow@xxxxxxxxxxxxxx>]

>
> 2. Use `--enable-cflags', `--enable-libs', `--enable-ldflags' or whatever.
> This probably ought to work because the arguments are remembered for use
> with --recheck.  But the guide for how configure is used is pretty
> fascistic about not allowing anything RMS wouldn't like, so I don't know if
> there are drawbacks to this.  Plus we need to be careful if people supply
> environment variables in the standard way.
>
> Does anyone know how to do this properly?
>

May be it is too late, but NEWS for current CVS autoconf says:

- Remembers environment variables when reconfiguring.
  The previous scheme to set envvar before running configure was
    ENV=VAL ./configure
  what prevented configure from remembering the environment in which
  it was run, therefore --recheck was run in an inconsistent
  environment.  Now, one should run
    ./configure ENV=VAR
  and then --recheck will work properly.  Variables declared with
  AC_ARG_VAR are also preserved.

It also has the whole bunch of new tests (64 bit, LFS, check for proper
function prototypes etc etc).

The CVS version was recently stamped with version number that probably
indicates it's relative "stableness" :-) If we commit to using it ... some
packages do (NTP being one). It also gives a chance to test autoconf before
release (at least, I'd be very interested to see if tests for 64bit/LFS really
work here).

-andrej