Well, yes, Autoconf had to go the compromise and detect *these* flags also when they were in the environment. But it only does so for a few common variables. You have to declare a variable as `precious' if you, the developer, want another variable recorded; see info Autoconf 'Setting Output Variables'
By the way, if you use AC_CONFIG_SUBDIRS, you may end up with a "parent configure" script that does not treat CFLAGS as a precious variable. But the "child configure" may need it.
If you type: ./config.status --version you will not see any 'CFLAGS'. But if you: ./child/config.status --version then you will. Andre Caldas. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
