Message48854
Logged In: YES
user_id=1266029
My second patch was indeed broken since it referred to $CC
before the call to AC_PROG_CC in configure.in. That caused
CC=gcc and CXX=c++ if neither --with-cxx-main nor CC was
given on the command line.
I am going to upload a third version (cxx-main.patch3) that
fixes this problem by moving the code that evaluates
--with-cxx-main below AC_PROG_CC.
To repeat what I wrote in my last comment: This patch does
not address the issue that distutils calls $CC in order to
compile C++ source files and calls $CXX in the linking step
only. Howevr, the patch tries to ensure that CXX is always
set to a sensible value in the Makefile - even if Python is
built exclusively with $CC. Thus, distutils has a fighting
chance to do the right thing (whatever that is) when
building C++ extensions since it uses the value of CXX
found in Python's Makefile. |
|
Date |
User |
Action |
Args |
2007-08-23 15:44:11 | admin | link | issue1324762 messages |
2007-08-23 15:44:11 | admin | create | |
|