This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: bump linkmap versions?
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Thu, 1 Aug 2002 09:56:50 -0700
- Subject: Re: bump linkmap versions?
- Organization: Red Hat / Chicago
- References: <20020731142702.605dc2a2.bkoz@redhat.com><ho8z3rvzn8.fsf@gee.suse.de><20020801095527.78bbea18.bkoz@redhat.com>
- Reply-to: bkoz at redhat dot com
> As the SONAME changed, you should start from scratch, ie. put all
> symbols into
> GLIBCPP_3.2 { ... }
> and
> CXXABI_1.2 { ... }
Ok that's what I thought. I'll do this too.
> But RSN on mainline GLIBCPP_3.3 {} version should be added and
> some automated process (in the regression tester) should be checking
> the exported symbols (and new ones should be always added to the
> new version).
Aaah. This is the part I cannot figure out. I don't have to do it
immediately, but I'd feel better if, at the very least, I could check
the exported symbols on 3.2 against the 3.2.0 release so I know that at
least the symbols stayed the same.
Right now I'm doing:
nm --extern-only --portability libstdc++.so.5.0.0 | awk '{ print $1 $2}'
>& symbols.txt
sort symbols.txt >& symbols_sorted.txt
For 3.2, 3.3, and diffing the bits.
-benjamin