Re: Bug(?) of libstdc++ (COW is still used)

Takashi Yano via Cygwin writes:
> Is there any reason that libstdc++ on Cygwin still uses COW
> (_GLIBCXX_USE_CXX11_ABI = 0 setting), even though it is inhibited
> since C++11?

I've inherited it that way and the reason it has not been changed is
still the same: Binary compatibility across binaries and (probably more
imporantly) libraries that were compiled with different settings breaks.
The Linux distributions avoided that outcome by a "rebuild the world"
event, but we might not be able to do that, at least not easily.

So no, you should not be nilly-willy changing that definition if you
compile a library that potentially gets used by other parts of Cygwin
(it is supposed to work correctly if it is only used by your
application).

You are free to analyze which packages would have to be rebuilt and
whether they actually still are buildable several compiler versions
later.  If it turens out we can do that, I'd be more than happy to
change that default.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple