Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: From: "Norman Vine" To: "David Abrahams" , Subject: RE: Cygwin GCC linking Python extensions issue Date: Fri, 23 May 2003 08:50:19 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal X-Virus-Scanned: Cape.Com VirusScan, no known virus found 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 HTH Norman -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/