BLD: don't statically link to libstdc++ #97
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Linking to libstdc++ statically causes weird memory errors when trying to import other extensions that link to it dynamically (e.g. matplotlib, contourpy). yt-project/yt#4910 is the same issue in yt.
This script should reproduce the crash:
Running python under gdb gives the following backtrace:
Details
As I understand it, the
std::locale
static initialization code runs a second time whenlibstdc++.so.6
is loaded by_contourpy
, which breaks some assumptions about the global state. Here's some discussion on the gcc-help mailing list about what is probably the same issue: https://gcc.gnu.org/legacy-ml/gcc-help/2017-05/msg00164.html.