Python interpreter unnecessarily linked against c++ runtime

[zak-k]

BPO	1254125
Nosy	@loewis

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2010-08-21.18:55:19.659>
created_at = <Date 2005-08-08.11:48:01.000>
labels = ['type-feature', 'build']
title = 'Python interpreter unnecessarily linked against c++ runtime'
updated_at = <Date 2010-08-21.18:55:19.657>
user = 'https://bugs.python.org/zak-k'

bugs.python.org fields:

activity = <Date 2010-08-21.18:55:19.657>
actor = 'BreamoreBoy'
assignee = 'none'
closed = True
closed_date = <Date 2010-08-21.18:55:19.659>
closer = 'BreamoreBoy'
components = ['Build']
creation = <Date 2005-08-08.11:48:01.000>
creator = 'zak-k'
dependencies = []
files = []
hgrepos = []
issue_num = 1254125
keywords = []
message_count = 3.0
messages = ['60798', '60799', '114543']
nosy_count = 3.0
nosy_names = ['loewis', 'zak-k', 'BreamoreBoy']
pr_nums = []
priority = 'low'
resolution = 'wont fix'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue1254125'
versions = ['Python 2.7']

[zak-k]

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 bpo-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.

[loewis]

Logged In: YES
user_id=21627

Would you like to contribute a patch?

If you merely look for a way to prevent linkage with
libstdc++, please configure --without-cxx.

[BreamoreBoy]

No reply to msg60799.