Logged In: YES 
user_id=1266029

That depends on how clever the patch is supposed to be. 
 
I am going to attach a patch against configure.in (from current 
CVS) that enforces `LINKCC = $(PURIFY) $(CXX)' if 
--with-cxx=<comiler> is passed to configure. My rationale is that a 
user who specifies --with-cxx wants python to be build with the 
C++ compiler and therefore won't mind if the executable depends 
on the C++ runtime library. 
 
The previous code in configure.in tried to determine if one can 
link the executable with the C compiler/linker even if some of the 
object files were compiled by a C++ compiler. The approach 
taken seems to be fragile, though: In simple cases g++ 4.0 seems 
to realize there is no need for the C++ runtime libraries, but in 
more complex cases it adds a dependency on the C++ runtime 
anyway. Even if you add a more complex test case to 
configure.in, how do you know your testcase mirrors the 
complexity of the python executable and any C++ extension 
loaded at runtime? I think a proper test would be quite involved 
whence I prefer the simplistic approach taken by my patch. 
 
Do you know a system / use case where one needs to compile 
python.c with a C++ compiler but needs to avoid the dependency 
on the C++ runtime? 
 
Regards 
 
Christoph