Christoph Ludwig [EMAIL PROTECTED] writes:
--with-cxx=compiler: If you plan to use C++ extension modules, then on some
platform you need to compile python's main() function with the C++
compiler. With this option, make will use compiler to compile main()
*and* to link
Christoph Ludwig [EMAIL PROTECTED] writes:
I do not claim the 2 TUs test will cover all possible scenarios. I am not even
sure this decision should be left to an automated test. Because if the test
breaks for some reason then the user is left with a linker error that is
time-consuming to
[Christoph, please keep the python-dev list in the loop here, at least
until they get annoyed and decide we're off-topic. I think this is
crucial to the way they package and deliver Python]
Christoph Ludwig [EMAIL PROTECTED] writes:
On Thu, Jul 07, 2005 at 06:27:46PM -0400, David Abrahams
David Abrahams wrote:
When I looked into this problem I saw that configure in fact builds a test
executable that included an object file compiled with g++. If the link step
with gcc succeeds then LINKCC is set as above, otherwise CXX is
used. Obviously, on my system this test was successful so
David Abrahams wrote:
I'm wondering if there has been a well-known recent change either in Python
or GCC that would account for these new reports. Any relevant
information would be appreciated.
So what about the theory that it may be that different versions of
libstdc++ get linked? Python is
Martin v. Löwis [EMAIL PROTECTED] writes:
David Abrahams wrote:
I'm wondering if there has been a well-known recent change either in Python
or GCC that would account for these new reports. Any relevant
information would be appreciated.
So what about the theory that it may be that different
Recently people testing Boost.Python with GCC on Linux have reported
that the extensions being tested have to be compiled with exactly the
same version of GCC as the Python they're being loaded into, or they
get mysterious crashes.
That doesn't correspond to my past experience; it has always
