target-specific contents for libstdc++: how to? [with actual patch!]

[Paolo Carlini]

Hi,

>It looks like other similar compatibility stuff goes in
>src/compatibility.cc.  Is that right?  More generally, is this patch
>right?  (The ugly bit is at the end.)  If not right, how should this
>be done?
>
Benjamin and Jakub introduced compatibility.cc to fix an annoying
problem and in my opinion are the most qualified people to answer your
question.

My personal point of view is that that file has been introduced for a
*very specific* reason (maybe not fully transparent from the name), that
is, exploit the alias extension in order to export some new symbols,
already exported (by mistake) as @GLIBCXX_3.4, also, correctly, as
@GLIBCXX_3.4.5. I think we all want to keep this generic file as small
as possible, in preparation for the eventual complete elimination.
Therefore, I would definitely encourage you to localize the
darwin-specific additions in the darwin-specific files.

Paolo.