-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 8/6/2008 4:41 PM: | But autoconf still hardwires this logic in _AC_PROG_CC_G: | | --------------------------------------------- | elif test $ac_cv_prog_cc_g = yes; then | if test "$GCC" = yes; then | CFLAGS="-g -O2" | | Could this be made customizable somehow? Either through a variable that the | developer could set in his configure.ac before the invocation of AC_PROG_CC, | or through a macro which he could redefine in his configure.ac?
Hmm. This is an interesting request, and seems doable. I think it would be reasonable to see this in the user's configure.ac, just prior to AC_PROG_CC: AC_PROG_GCC_DEFAULT_FLAGS([-O2 -g -Wall]) at which point, that string becomes the first set of CFLAGS tried for the compiler (if $CFLAGS is undefined), before falling back on "-g -O2" if it didn't work. Anyone care to contribute a patch, even if only to add a line in the TODO file pointing to this thread? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiaTfQACgkQ84KuGfSFAYCSOgCfbXBshx8qxuNGqq4b1XrFXWMM 3d4AoIGeog8Mav1XA67JcrxJS5JtQHZQ =KlL+ -----END PGP SIGNATURE-----
