googlecloudprofiler breaks other packages which depend on C++ code compiled against a different version of libstdc++

[danking]

These lines here,

cloud-profiler-python/setup.py

Lines 46 to 53 in ea964fc

	'-static-libstdc++',
	# While libgcc_s.so.1 is pretty much always installed by default
	# for non-Alpine linux, it is not installed by default in Alpine.
	# So, to support Alpine, we will always statically link "libgcc"
	# package. We could alternatively require users to install the
	# "libgcc" package, but the static linkage seems less
	# invasive.
	'-static-libgcc'

statically link this package's native code against the particular version of libstdc++ available at link time. This breaks other packages which have native code and depend on a different version of libstdc++.

It seems reasonable to me to ask your users to have a recent version of libstdc++ and libgcc available. Or perhaps you could publish two packages to PyPI, this one and one that uses a dynamic link?

Thanks!

PS: I discovered this because version 4.0.0 is incompatible with libsass.

[punya]

Would hiding symbols (pypa/auditwheel#125 (comment)) also solve the problem?