From: Rene Rivera (grafik.list_at_[hidden])
Date: 2003-12-26 19:32:54
David Abrahams wrote:
> David Abrahams <dave_at_[hidden]> writes:
>>>* Boost.Python doesn't build in MinGW. I've tried looking at this one
>>> but it seems to be a problem with the way MinGW exports variables in
>>> a DLL.
>>Whoa, that's a new one on me. I'd been testing Boost.Python with
>>MinGW for quite some time. I'll see if I can reproduce this one.
> Hmm, it's working for me. What problems are you seeing?
If you look at the build logs...
You'll see my errors.
Cannot export .idata$4: symbol not found
Cannot export .idata$5: symbol not found
Cannot export .idata$6: symbol not found
Cannot export .text: symbol not found
Cannot export python22_NULL_THUNK_DATA: symbol not found
Creating library file:
C:/CVSROOTs/Boost/boost/libs/python/src/numeric.cpp:29: undefined reference to
C:/CVSROOTs/Boost/boost/libs/python/src/numeric.cpp:57: undefined reference to
And so on for all references to Python exported globals.
Which version of MinGW are you using? And how are you building?
I'm at MinGW 3.1.0-1, which is GCC 3.2.3.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera_at_[hidden] - grafik_at_[hidden] - 102708583_at_icq
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk