This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin GCC linking Python extensions issue
- From: David Abrahams <dave at boost-consulting dot com>
- To: <nhv at cape dot com>
- Cc: <cygwin at cygwin dot com>
- Date: Fri, 23 May 2003 09:47:42 -0400
- Subject: Re: Cygwin GCC linking Python extensions issue
- References: <EKEJIKAILPONGGENMBGAEEELDIAA.firstname.lastname@example.org>
"Norman Vine" <email@example.com> writes:
> David Abrahams writes:
>> Recently I've begun to see the following link errors when building
>> some of the Boost.Python test suite extension modules using Cygwin gcc
>> (version 2 or 3, doesn't matter) and Python 2.2.2 release or Python
>> 2.3 debug. This error happens only on some of the extension modules,
>> but all of them use the symbol boost::python::scope::current_scope
>> which is defined in libboost_python.dll. Regardless, even if that's
>> somehow my bug, there's the matter of `__head_boost_python_dll'...
>> Does anyone have an explanation/workaround for this?
>> d000000.o(.idata$2+0x0): multiple definition of
> Tell the linker multiple definitions are allowed by adding
> '-Wl,--allow-multiple-definition' to your $LD_FLAGS
That's an interesting idea. Still, I'd like to get to the bottom of
this. Why would it think there are multiple definitions for these
symbol? AFAICT, there are not.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html