Re: preliminary libstdc++ ABI docs

[Phil Edwards <phil at jaj dot com>]

> > Should that number have any relation to configure.in's
> > libtool_VERSION, which also tracks the ABI?  (Everyone remember that
> > the "version" in the map file is just a text string and does not need
> > to be able to be "calculated" like a libtool version would, or any
> > other version for that matter.  I would think that "3.1" should be
> > either "3.2" or "5".)
> 
> Looking at libgcc_s, as well as glibc, it looks like 3.2.

Or maybe 3.3, given the version renumbering?


> > Should a new GLIBCPP_foo inherit the symbols from GLIBCPP_3.1?  I
> > think it's supposed to work that way, but this breaks new ground for
> > me.
> 
> Not quite sure what you are getting at here.

In a build directory on linux, take a look at gcc/libgcc/libgcc.map:

    GCC_3.0 {
        ...some symbols...
    } GLIBC_2.0;

The symbols associated with GCC_3.0 are inheriting version information from
GLIBC_2.0.  I can't adequately explain this (like I say, new ground for me),
but I can point ya to docs.sun.com's "Linker and Libraries Guide" in the
software developer collection.  They have a good chapter on versioning,
with examples.  GNU ld chose to follow their design.



Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams