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 doko, lemburg, rpetrov
Date 2010-05-03.18:11:14
SpamBayes Score 7.23974e-05
Marked as misclassified No
Message-id <>
In-reply-to <>
Matthias Klose wrote:
> Matthias Klose <> added the comment:
> my understanding is that the builder is allowed to overwrite OPT, but not BASECFLAGS.

The builder should actually be allowed to override the complete
CFLAGS and LDFLAGS settings, but for historic reasons, this is
currently not possible and you're right: OPT was meant to be overridden
by the user and BASECFLAGS is reserved for configure use.

Since just adding the CFLAGS to the linker invokation breaks on
various platforms (the linker doesn't expect compiler flags or
complains due to duplicate flags), this simple route will not work.

I suppose the best way to do this is by adding an extra check
to that tests whether the new GCC 4.5 option is supported
and also check whether CFLAGS can be passed to the
linker. If this test succeed, the configure script could then
add CFLAGS to the linker invokations or perhaps merge CFLAGS into
Date User Action Args
2010-05-03 18:11:18lemburgsetrecipients: + lemburg, doko, rpetrov
2010-05-03 18:11:16lemburglinkissue8535 messages
2010-05-03 18:11:14lemburgcreate