Message60798
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.
|
|
Date |
User |
Action |
Args |
2008-01-20 09:58:06 | admin | link | issue1254125 messages |
2008-01-20 09:58:06 | admin | create | |
|