[PATCH] ia64 libgcc routines for binary compatibility
Ulrich Drepper
drepper@redhat.com
Fri May 3 00:14:00 GMT 2002
On Thu, 2002-05-02 at 10:08, Jakub Jelinek wrote:
> All of these are used internally by glibc anyway, so IMHO just exporting
> them normally will make various binaries/libraries tiny bit smaller,
> but if you prefer to export them as @GLIBC_2.0 symbols only (ie. nobody
> will be able to link against them), so be it.
I really hate doing this. It never should have happened. But the least
we can do is to limit the damage. I don't want to track libgcc and it
should also be possible to build a legacy-free system. This is why I've
added patches to export the code via version GLIBC_2.2. It's untested.
If it does not work for you (or does work) let me know so I can carry
the change over to the 2.2 branch.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
URL: <http://sourceware.org/pipermail/libc-hacker/attachments/20020503/465d9dc3/attachment.sig>
More information about the Libc-hacker
mailing list