[Python-Dev] [C++-sig] GCC version compatibility (original) (raw)

Ralf W. Grosse-Kunstleve rwgk at yahoo.com
Sun Jul 10 16:13:02 CEST 2005

--- David Abrahams <dave at boost-consulting.com> wrote:

Christoph Ludwig <cludwig at cdc.informatik.tu-darmstadt.de> 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 track down. However, at least by the usual hierarchy of values, the sort of runtime error that results from the current needless linking with C++ on ELF/Linux is even worse.

Indeed. A few months ago the current configure behavior lead to a major loss of our time, probably a whole week between 4-5 people. The problem was that a Python compiled under RH 8.0 was used to build and run new C++ extensions under Fedroa Core 3. Some extensions ran OK, others crashed without warning after running to a certain point. It was very confusing. To avoid this situation in the future, we permanently added a test to our setup scripts, comparing the result of ldd python | grep libstdc++ to the corresponding output for extension modules.

Cheers, Ralf

Sell on Yahoo! Auctions – no fees. Bid on great items.
http://auctions.yahoo.com/

More information about the Python-Dev mailing list