.../configure CFLAGS=-g
That may be a clean approach, but running configure is slow enough as it
is; re-running it for trivial changes is really aggravating.
You would have to "make clean" anyway!!
If you need to switch that much between CFLAGS definitions, then maybe
you should have two build trees.
If you want to memorialize the change (instead of just relying on
overriding the setting at make invocation) the other obvious choice is
to edit the config.status script and re-run that to propagate the
changes to the Makefiles.
The file config.status is a generated file. I would not advise anyone
to edit a generated file.
I myself like to use
./config.status --version
to check for the arguments passed to it and re-run the configure
script. By your method, I would have to remember what to change in
"config.status" everytime!
Andre Caldas.
_______________________________________________
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
