Ed Hartnett wrote:
In a similar situation, I first check to see if CFLAGS is set, then
only muck with it if it has not been set:
Yes, we do something similar in FFTW.
To those on this list who think that configure should never set CFLAGS,
realize that optimizing CFLAGS can be very important for
high-performance scientific programs and requiring the user to set them
is painful and error-prone. (Of course, you want the user to be able to
override them if necessary.)
See AX_CC_MAXOPT (http://autoconf-archive.cryp.to/ax_cc_maxopt.html) at
the macro archive for the macro that FFTW uses to set its flags
depending on the compiler vendor, architecture, etcetera.
Regards,
Steven G. Johnson
_______________________________________________
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
