Re: [Boost-bugs] [Boost C++ Libraries] #8414: flyweights causes weird library initialization error

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8414: flyweights causes weird library initialization error
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-04-08 15:19:00

#8414: flyweights causes weird library initialization error
-----------------------------------------------------------+----------------
  Reporter:  charles quarra <charlls_quarra@…>             |       Owner:  joaquin    
      Type:  Bugs                                          |      Status:  closed     
 Milestone:  To Be Determined                              |   Component:  flyweight  
   Version:  Boost 1.53.0                                  |    Severity:  Showstopper
Resolution:  invalid                                       |    Keywords:             
-----------------------------------------------------------+----------------

Comment (by joaquin):

 Yep, my fault, I skimmed through the test case and thought the referred to
 commandline was the one used for building the main executable.

 OK, so we have `dlclose` failing for no apparent reason (can you confirm
 `dlclose` indeed returns something !=0?) Boost.Flyweight creates static
 objects for the value factory using this so-called holder:

 {{{
 template<typename C>
 struct static_holder_class:holder_marker
 {
   static C& get()
   {
     static C c;
     return c;
   }
 };
 }}}

 which looks suspiciously similar to the problem described at

 http://stackoverflow.com/questions/11050693/dlclose-doesnt-work-with-

 factory-function-complex-static-in-function

 Could you try using `--no-gnu-unique` as desribed in the post above?

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