I was building Python 2.2.1 on Debian/GNU Linux 3.0
(testing pre-release) with gcc and g++ of version 3.0.4,
using  --with-cxx=g++ configure option. Then linking of the
"python" executable fails due to an unresolved symbol
(__gxx_personality_v0) in Modules/ccpython.o, because
linking is still done with gcc: LINKCC is set to gcc ($CC)
by configure, rather than to g++ ($CXX).

The configure script attempts to determine the value of
LINKCC and sets it to $CC if the latter can
successfully link
the simplest program "int main(){return 0;}" which was
compiled with $CXX. In this case, linking apparently
succeeds, setting LINKCC to $CC. Yet linking of
Modules/ccpython.o with $CC fails,  probably because
Modules/ccpython.c is slightly more complex than the
above configuration test, hence an extra unresolved
symbol generated by g++.

I am not sure how the correct value of LINKCC can be
determined at config time without unnecessarily using
$CXX all the time when it is available. Maybe the
makefile should be modified so it always starts from
$CC and falls through to $CXX if the former fails?

Sincerely,
Dr. Leonid Timochouk
Computing Laboratory
University of Kent at Canterbury
England

Logged In: YES 
user_id=33168

I believe there were some changes made which should fix this
problem.  Can you try the latest CVS for the 2.2 branch or
2.3?  

cvs update -r release22-maint 
will get the 2.2.1+ version (what will become 2.2.2).

Thanks.

Logged In: YES 
user_id=11375

As Neal suggested, this problem seems to be fixed in Python 2.2.2 and 2.3CVS.  Marking as closed.