Ronald Oussoren <ronaldousso...@mac.com> added the comment: 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 ---------- versions: +Python 2.6, Python 3.1 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8366> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
