Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4594: Boost exception classes do not have GCC default visibility
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2014-10-20 17:29:49
#4594: Boost exception classes do not have GCC default visibility
------------------------------------------------+--------------------------
Reporter: Jonathan Jones <jonathan.jones@â¦> | Owner:
Type: Patches | emildotchevski
Milestone: To Be Determined | Status: closed
Version: Boost 1.47.0 | Component: exception
Resolution: fixed | Severity: Showstopper
| Keywords:
------------------------------------------------+--------------------------
Comment (by anonymous_but_0X):
Hello everyone,
hope you had a good weekend, I am afraid the problem is back,
moving from LLVM xcode 4.4.1 to Apple LLVM 6.0 (10.9), I got it again, but
I think I am not the only one.
"boost::exception_detail::error_info_injector
<boost::gregorian::bad_month>::error_info_injector(boost::exception_detail::error_info_injector<boost::gregorian::bad_month>
const&) to global weak symbol vtable for
boost::exception_detail::error_info_injector<boost::gregorian::bad_month>
means the weak symbol cannot be overridden at runtime. This was likely
caused by different translation units being compiled with different
visibility settings."
the mysterious thin, and I think I need to question Ted Kremenek, because
with the previous LD/compiler everything was fine according to their
static analyzer, moving to the next version tool makes it incompatible,
weak symbols that's just a convention how you stored them, Kremenek should
use its magic wand and give solution.r
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/4594#comment:21> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:17 UTC