[Python-bugs-list] [ python-Bugs-569668 ] LINKCC incorrectly set

noreply@sourceforge.net noreply@sourceforge.net
Wed, 13 Nov 2002 17:53:04 -0800

Bugs item #569668, was opened at 2002-06-16 11:12
You can respond by visiting: 

Category: Build
Group: Python 2.2.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Dr Leonid A Timochouk (cardou)
>Assigned to: A.M. Kuchling (akuchling)
Summary: LINKCC incorrectly set

Initial Comment:
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?

Dr. Leonid Timochouk
Computing Laboratory
University of Kent at Canterbury


Comment By: Neal Norwitz (nnorwitz)
Date: 2002-09-06 18:29

Logged In: YES 

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

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



You can respond by visiting: