undefined symbol: __dso_handle with current CVS breaks C++

[Martin v. Loewis]

> Do you mean "-fPIC" as distinct from "-fpic", or will either do?

That should not matter on x86.

> Because I've built libstdc++-v3 with it as a shared object, but I
> suppose it's possible that libstdc++-v3 might still function even if
> __dso_handle is busted.

Indeed. I'm not sure what would happen if you try to access a .hidden
variable (as opposed to a .hidden function); most likely, you'd access
some random location.

Regards,
Martin