Re: [Boost-bugs] [Boost C++ Libraries] #2615: boost 1.37.0 does not link against libpython

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2615: boost 1.37.0 does not link against libpython
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-12-29 19:41:13

#2615: boost 1.37.0 does not link against libpython
----------------------------------+-----------------------------------------
  Reporter:  fundawang_at_[hidden]  |       Owner:  dave          
      Type:  Bugs                 |      Status:  reopened      
 Milestone:  Boost 1.38.0         |   Component:  Building Boost
   Version:  Boost 1.37.0         |    Severity:  Problem       
Resolution:                       |    Keywords:                
----------------------------------+-----------------------------------------
Changes (by jhunold):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 I think that "direct linking" against libpython.so (for dynamic linking
 only, of course) will not embed the symbols in libboost_python.so, but
 enable the linker to verify that all weak references into libpython.so can
 be resolved at runtime. Using "--no-undefined" is a way to check that you
 explicitly link against _all_ required libraries. If linking "normally"
 gnu ld will link everything together happily (with weak symbols) and trust
 the runtime loader to pull everything together. In this case, your builds
 might fail on the windows platform for example where the msvc linker (and
 dllexport/-import) always enforce explicit listing of all needed libraries
 at link time. Qt > 4.3 uses this flag to improve cross platform
 consistency (in addition to gcc visibility support).

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/2615#comment:3>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.