Boost C++ Libraries: Ticket #11560: Error: Linker scopes may not change after symbol definition for serialization. https://svn.boost.org/trac10/ticket/11560 <p> This is my attempt to separate the serialization issues from the regex issues of ticket <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/11544" title="#11544: Bugs: Error: Linker scopes may not change after symbol definition. (closed: fixed)">#11544</a>. </p> <p> I compiled Boost 1.59.0 with Solaris Studio 12.4 in C++11 mode and I get the following error messages: </p> <p> "libs/serialization/src/basic_archive.cpp", line 45: Error: Linker scopes may only be more restrictive. "libs/serialization/src/basic_archive.cpp", line 79: Error: Linker scopes may only be more restrictive. "libs/serialization/src/basic_xml_archive.cpp", line 18: Error: Linker scopes may only be more restrictive. "libs/serialization/src/basic_xml_archive.cpp", line 22: Error: Linker scopes may only be more restrictive. "libs/serialization/src/void_cast.cpp", line 315: Error: Linker scopes may only be more restrictive. "libs/serialization/src/void_cast.cpp", line 349: Error: Linker scopes may only be more restrictive. </p> <p> My temporary solution was to delete the following lines from boost/config/compiler/sunpro_cc.hpp: </p> <pre class="wiki">// // Dynamic shared object (DSO) and dynamic-link library (DLL) support // #if __SUNPRO_CC &gt; 0x500 # define BOOST_SYMBOL_EXPORT __global # define BOOST_SYMBOL_IMPORT __global # define BOOST_SYMBOL_VISIBLE __global #endif </pre> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/11560 Trac 1.4.3 Robert Ramey Tue, 29 Sep 2015 21:23:46 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/11560#comment:1 https://svn.boost.org/trac10/ticket/11560#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> I think this is fixed now </p> Ticket