|
Boost : |
From: Neal D. Becker (ndbecker2_at_[hidden])
Date: 2004-04-26 06:50:18
Vladimir Prus wrote:
> Hi Neal,
>
>> I have both added current program-options to my boost build tree, and all
>> the usual variants of libboost_program_options-gcc.a, also
>> libboost_python-gcc-mt.a.
>>
>> Linking against libboost_program_options-gcc.a I get errors about pthread
>> symbols. Adding -pthread fixes it. It looks to me that
>> libboost_program_options-gcc.a
>> is referencing pthread symbols.
>>
>> nm
>> /usr/local/src/boost_1_31_0.gcc34/stage/lib/libboost_program_options-gcc.a
>> | grep thread
>> U pthread_mutex_destroy
>> U pthread_mutex_init
>> w pthread_mutex_lock
>> w pthread_mutex_unlock
>> w pthread_mutex_lock
>> w pthread_mutex_unlock
>>
>> Yup,sure is.
>
> Interesting, I sure don't use any mutexes directly. This could be because
> I use shared_ptr which uses boost::mutex in MT builds. Maybe, you're using
> MT build of the program_options library?
>
No, as the above shows, the symbols are in the non-mt version of the
library. There is also libboost_python-gcc-mt.a, that's not the one I'm
showing above.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk