➜

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 ronaldoussoren
Recipients l0nwlf, ned.deily, ronaldoussoren, rpetrov, vstinner
Date 2010-04-18.15:41:33
SpamBayes Score 1.0486723e-11
Marked as misclassified No
Message-id <1271605295.62.0.239727234745.issue8366@psf.upfronthosting.co.za>
In-reply-to
Content 
This problem is caused by this bit in Makefile.pre.in:

OPT=            @OPT@
BASECFLAGS=     @BASECFLAGS@
CFLAGS=         $(BASECFLAGS) @CFLAGS@ $(OPT) $(EXTRA_CFLAGS)


There both 'BASECFLAGS' and 'CFLAGS' get patched in from configure.in, while the intention of the configure script always was that only BASECFLAGS gets set from configure CFLAGS. 


BTW. I always test with a build directory separate from the source directory, that makes it a lot easier to ensure that you have a clean environment:

$ mkdir build
$ cd build
$ ../configure ....


I'm currently testing a fix that only sets CFLAGS and CPPFLAGS and will apply that if this results in a valid build.


Adding 2.6 and 3.1 to the list of versions because those also have the same change to Makefile.pre.in
History
Date User Action Args
2010-04-18 15:41:35ronaldoussorensetrecipients: + ronaldoussoren, vstinner, ned.deily, rpetrov, l0nwlf
2010-04-18 15:41:35ronaldoussorensetmessageid: <1271605295.62.0.239727234745.issue8366@psf.upfronthosting.co.za>
2010-04-18 15:41:34ronaldoussorenlinkissue8366 messages
2010-04-18 15:41:33ronaldoussorencreate