This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Understanding gnu.ver and symbol exporting.
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Chris Fairles <chris dot fairles at gmail dot com>
- Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: Tue, 07 Oct 2008 14:30:39 +0200
- Subject: Re: Understanding gnu.ver and symbol exporting.
- References: <fac6bb500810070514j1dedd3d6la60f0af2ba6e948a@mail.gmail.com>
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.