RetroSearch Browse

Sun Jun 27 22:04:56 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-June/101154.html

On Sun, Jun 27, 2010 at 6:46 AM, Jeffrey Yasskin <jyasskin at gmail.com> wrote:
> AC_PROG_CC is the macro that sets CFLAGS to -g -O2 on gcc-based
> systems (http://www.gnu.org/software/hello/manual/autoconf/C-Compiler.html#index-AC_005fPROG_005fCC-842).
> If Python's configure.in sets an otherwise-empty CFLAGS to -g before
> calling AC_PROG_CC, AC_PROG_CC won't change it. Or we could just
> preserve the users CFLAGS setting across AC_PROG_CC regardless of
> whether it's set, to let the user set CFLAGS on the configure line
> without stomping any defaults.

I think saving and restoring CFLAGS across AC_PROG_CC was attempted in
http://bugs.python.org/issue8211 . It turned out that it broke OS X
universal builds.

I'm not sure I understand the importance of allowing AC_PROG_CC to set
CFLAGS (if CFLAGS is undefined at the point of the AC_PROG_CC);  can
someone give an example of why this is necessary?

Mark

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-June/101154.html below:

[Python-Dev] what environment variable should contain compiler warning suppression flags?