This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients Arfrever, lemburg, loewis, vstinner
Date 2010-03-23.19:17:44
SpamBayes Score 2.0408675e-11
Marked as misclassified No
Message-id <4BA913D7.6040309@egenix.com>
In-reply-to <1269370423.99.0.274063836288.issue8211@psf.upfronthosting.co.za>
Content
STINNER Victor wrote:
> 
> STINNER Victor <victor.stinner@haypocalc.com> added the comment:
> 
>> (or to fix it, but that's a major task - the whole CFLAGS 
>> and LDFLAGS system used in Python's configure has over the
>> years turned into a complete mess).
> 
> What do you mean by "a complete mess"? 

There's a discussion on some other ticket about this. Basically,
Python's configure script doesn't really allow setting CFLAGS
in a meaningful way via env vars (which it should to be standards
conform).

It adds all sorts of non-standard variables which are then combined
to build the final CFLAGS variable: BASECFLAGS, EXTRA_CFLAGS and
OPT.

> Did you try my patch? Is it enough to fix this issue?

No. It doesn't allow overriding the CFLAGS settings actually
used by the system. You'd also need to set BASECFLAGS="", OPT="" and
EXTRA_CFLAGS="" in addition to applying your patch and setting
CFLAGS to "-O0".

> A least, my patch is enough to disable all compilation optimization if --with-pydebug option is used (which was my first goal).

It unconditionally overrides CFLAGS - even if it is not set and
defined by AC_PROG_CC as "-g -O2". That would need to be corrected.

Other than that it does help a little work around the mess :-)
History
Date User Action Args
2010-03-23 19:17:47lemburgsetrecipients: + lemburg, loewis, vstinner, Arfrever
2010-03-23 19:17:45lemburglinkissue8211 messages
2010-03-23 19:17:44lemburgcreate