From: David Abrahams (dave_at_[hidden])
Date: 2006-07-13 10:08:23
Vladimir Prus <ghost_at_[hidden]> writes:
>> I also note this:
>> # NOTES:
>> # - V1 had logic to force intel to use gcc's runtime.
>> # Note sure why that was needed, with icc 8.0 extensions
>> # built with intel are loaded by python without problems.
>> Has the version of Python also been built with Intel?
> No, it's stock system Python. I don't think I ever built Python in life ;-)
>> If so you won't
>> see any problems, as the following v1 comment indicates:
>> # Normally on Linux, Python is built with GCC. A "poor QOI choice"
>> # in the implementation of the intel tools prevents the use of
>> # intel-linked shared libs by a GCC-built executable unless they
>> # have been told to use the GCC runtime. This rule adds the
>> # requisite flags to the compile and link lines.
I think this *might* be a change they made in Intel 9.0, which is why
you're not seeing a problem. I had an extensive discussion about this
with Intel's support people because it *was* a real problem. Ralf, do
you remember this issue? Maybe it has to do with rtti or exceptions
not working across .so boundaries?
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk