[ python-Bugs-1254125 ] Python interpreter unnecessarily linked against c++ runtime

[SourceForge.net]

Bugs item #1254125, was opened at 2005-08-08 12:48
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1254125&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Zak Kipling (zak-k)
Assigned to: Nobody/Anonymous (nobody)
Summary: Python interpreter unnecessarily linked against c++ runtime

Initial Comment:
By default, on an ELF-based Linux system with a working
g++, the configure script will choose to build a C++
wrapper for main(). This causes the resulting
interpreter executable to be linked against libstdc++.
However, the comments in  bug #224782 suggest that this
is not necessary in order to support C++ extension
modules on ELF (unlike a.out).

Would it be possible for Modules/ccpython.cc to be used
only on those systems that don't correctly support
dynamically loading C++ code from C executables?

I'm currently seeing this with Python 2.4.1, on a
Gentoo ~amd64 system.



----------------------------------------------------------------------

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