Understanding gnu.ver and symbol exporting.

Paolo Carlini paolo.carlini@oracle.com
Tue Oct 7 12:31:00 GMT 2008


Hi Chris,
> Adding this to gnu.ver, I get 4 abi failures, the last 3 future_error
> symbols and the allocator_arg. So I'm missing something, and I'm
> pretty sure it has to do with that extern "C++" block at the top of
> the file. First, there's no std::f* section so do I have to do
> something like:
>
> std::f[a-t]*;
> #std::future_error
> std::future[^_]*;
> std::f[v-z]*;
>   
hard to help for your specific problem in such a way, in the abstract...

Anyway, in general, I can tell you something for sure: that "C++" block
belongs to GLIBCXX_3.4, thus during the normal development work you are
**never** adding exports to it. Only, from time to time, you have to
tweak it in order to *avoid* the existing patterns to match
inadvertently the names of new symbols, which of course are exported as
GLIBCXX_3.4.11. I hope that helps...

Paolo.



More information about the Libstdc++ mailing list