[Python-bugs-list] [ python-Bugs-472007 ] Linker problem on HP-UX 11.00 (original) (raw)

noreply@sourceforge.net noreply@sourceforge.net
Wed, 17 Oct 2001 06:29:22 -0700

Bugs item #472007, was opened at 2001-10-17 01:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105470&aid=472007&group_id=5470

Category: Build Group: Python 2.2 Status: Open Resolution: None Priority: 5 Submitted By: Richard Townsend (rptownsend)

Assigned to: Nobody/Anonymous (nobody) Summary: Linker problem on HP-UX 11.00

Initial Comment: I use the following command to run the configure script:

CC=cc
OPT="+DAportable"
INSTALL="./install-sh -c"
./configure --with-threads --without-gcc
--with-cxx=/opt/aCC/bin/aCC --without-libd
--with-cycle-gc --prefix=/opt/python
--exec-prefix=/opt/python

In the Makefile I get the following lines:

CC= cc -Ae CXX= /opt/aCC/bin/aCC LINKCC= (PURIFY)(PURIFY) (PURIFY)(CC)

The build then fails with:

/usr/ccs/bin/ld: Unsatisfied symbols: _main (first referenced in Modules/ccpython.o) (code) *** Error exit code 1

If I edit the Makefile, thus:

CC= cc -Ae CXX= /opt/aCC/bin/aCC LINKCC= (PURIFY)(PURIFY) (PURIFY)(CXX)

The builds succeeds.

Comment By: Martin v. L�wis (loewis) Date: 2001-10-17 06:29

Message: Logged In: YES user_id=21627

LINKCC already was set to CXX before (configure.in 1.113); that was undone later (1.198). Unfortunately, none of these checkins indicate why they have been done; I recall that people where complaining that python requires libstdc++ on Linux.

I've now designed a test that checks whether CXX must be used to link if main() was compiled with CXX. I cannot test it on a system that has this property, so I'll attach it to this report.

When patching configure fails for you, please re-run autoconf. If you don't have autoconf, please fix the two line numbers in the patch to match your configure; the patch should apply then.

Comment By: Guido van Rossum (gvanrossum) Date: 2001-10-17 05:36

Message: Logged In: YES user_id=6380

Martin, do you understand the logic in configre.in enough to suggest a patch? If not, please unassign it.

You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105470&aid=472007&group_id=5470