Re: Checks-syms results

[Roland McGrath]

> I've rerun the script on the current set of installed binaries, so
> that you have the information for now.

Thanks.  It occurs to me that in case I tweak the script more you might as
well just give me the full output of objdump * to process myself.
I am presuming that it won't be very large once compressed.

In fact, the new output looks a little suspect so I probably need to debug
the awk code a bit.

I would also like to get the symbols from all the shared objects, not just
binaries.  But specifically excluding all the ones from the libc and hurd
packages.

> libgcc_s.so.1 appears to have it.  I suspect it's from the file
> gcc-3.0.3/gcc/config/libgcc-glibc.ver

Ah, ok.  If you're saying libgcc_s.so.1 makes those weak references
and nothing else uses the GLIBC_2.0 set at all, then that is fine.

> Will I see this change in "hurd" or in "glibc"?  (So I know where to
> look before I start recompiling)

It's in libc.  

> Question - Do you have a plan for what makes it a "0.3" ABI vs. a
> "1.0" ABI?  If this should be a fairly stable and long term change, it
> might be nice to have at least something of ours at a 1.0 stage.

:-) Well, it's still not perfect yet.  And hey, GNU Mach is at 1.2!  When
we finally mainline oskit-mach I will be more than happy to call it 2.0 if
that makes you feel extra warm and fuzzy.  

Despite my best intentions, I still think all our current ABIs are just a
draft and we might be doing this all over again before we're happy.  It's
possible that the final integrated pthreads and signal rewrite will happen
without losing current ABI compatibility, but being realistic I have to be
a bit skeptical.  I still want to have another ABI shift with more
libraries or more nuanced use of symbol versions, or something, so as to
distinguish programs that use the POSIX/generic-GNU parts of the ABI vs
Hurd-specific functions and such.  It could be that that shift can also be
the one to harmonize with the (future or current, as it goes) GNU/Linux
ABIs.  That could be the next shift or there could be some in between.