This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] ia64 libgcc routines for binary compatibility

From: Ulrich Drepper <drepper at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Glibc hackers <libc-hacker at sources dot redhat dot com>
Date: 03 May 2002 00:14:37 -0700
Subject: Re: [PATCH] ia64 libgcc routines for binary compatibility
References: <20020502190823.N32482@sunsite.ms.mff.cuni.cz>

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   `------------------------

Attachment: signature.asc
Description: This is a digitally signed message part

References:
- [PATCH] ia64 libgcc routines for binary compatibility
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]