RetroSearch Browse

Sat Jun 26 22:40:07 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-June/101127.html

Brett Cannon wrote:
> I finally realized why clang has not been silencing its warnings about
> unused return values: I have -Wno-unused-value set in CFLAGS which
> comes before OPT (which defines -Wall) as set in PY_CFLAGS in
> Makefile.pre.in.
>
> I could obviously set OPT in my environment, but that would override
> the default OPT settings Python uses. I could put it in EXTRA_CFLAGS,
> but the README says that's for stuff that tweak binary compatibility.
>
> So basically what I am asking is what environment variable should I
> use? If CFLAGS is correct then does anyone have any issues if I change
> the order of things for PY_CFLAGS in the Makefile so that CFLAGS comes
> after OPT?

It is not important to me as flags set to BASECFLAGS, CFLAGS, OPT or 
EXTRA_CFLAGS will set makefile macros CFLAGS and after distribution 
python distutil will use them to build extension modules. So all 
variable are equal for builds.

Also after configure without OPT variable set we could check what script 
select for build platform and to rerun configure with OPT+own_flags set 
on command line (! ;) ) .

Roumen

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

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

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