https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67903
--- Comment #6 from Jonathan Wakely ---
(In reply to Yucheng Low from comment #5)
> - We compile as a shared library to be imported into Python as part of a
> python
> module.
> - We want to use C++11 features yet we want to be able to run on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67903
--- Comment #5 from Yucheng Low ---
After some deep investigation on a related issue, I think might finally have a
root cause.
Introduction
- We compile as a shared library to be imported into Python as part of a
python
module.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67903
--- Comment #4 from Yucheng Low ---
I have tried version scripts and it ought to work but I couldn't quite figure
out what symbols to hide.
In any case, the proposed modification does fix a questionable bit of code in
locale.cc (i.e. the resize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67903
--- Comment #3 from Jonathan Wakely ---
(If this is something that should be fixed in the library at all),
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67903
--- Comment #2 from Jonathan Wakely ---
(In reply to Yucheng Low from comment #0)
> This would not be a problem if not for the fact that:
> - the global locale is initialized with an inplace new:
> locale_init.cc:378
> _M_fac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67903
--- Comment #1 from Richard Biener ---
To me it looks like the issue is that when statically linking libstdc++ into a
shared library you export the symbols of that libstdc++ copy and thus they
participate in merging. So my suggestion is that you
