Re: [Boost-bugs] [Boost C++ Libraries] #8810: Link error on some platforms: undefined reference to `boost::atomics::detail::lockpool::get_lock_for(void const volatile*)'

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8810: Link error on some platforms: undefined reference to `boost::atomics::detail::lockpool::get_lock_for(void const volatile*)'
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-07-12 17:05:30

#8810: Link error on some platforms: undefined reference to
`boost::atomics::detail::lockpool::get_lock_for(void const volatile*)'
-----------------------------------------+--------------------------
  Reporter:  Gennady  Proskurin <gpr@…>  |      Owner:  viboes
      Type:  Bugs                        |     Status:  assigned
 Milestone:  To Be Determined            |  Component:  thread
   Version:  Boost 1.54.0                |   Severity:  Problem
Resolution:                              |   Keywords:  get_lock_for
-----------------------------------------+--------------------------

Comment (by viboes):

 You are right, my apologies. Boost.Thread links already for PGI and VACPP
 compilers as for these compilers Boost.Atomic is not header only.

 {{{
     if <toolset>pgi in $(properties)  || <toolset>vacpp in $(properties)
     {
       result += <library>/boost/atomic//boost_atomic ;
     }
 }}}

 It seems that cross compiling is breaking the header-only feature of
 Boost.Atomic.
 I don't know if Boost.Thread/Boost.Atomic work well while cross compiling.

 Could you confirm the same error if you compile for the host?
 Could you check why Boost.Atomic is not header only in your case?

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