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: problems with ctype...

From: "H. J. Lu" <hjl at lucon dot org>
To: Roland McGrath <roland at redhat dot com>
Cc: Andreas Jaeger <aj at suse dot de>,GNU libc hacker <libc-hacker at sources dot redhat dot com>
Date: Mon, 16 Sep 2002 22:00:20 -0700
Subject: Re: problems with ctype...
References: <20020916080738.C2206@lucon.org> <200209170454.g8H4sPl03090@magilla.sf.frob.com>

On Mon, Sep 16, 2002 at 09:54:25PM -0700, Roland McGrath wrote:
> > They are real bugs exposed by glibc 2.3 and gcc 3.2. Please ask users
> > to upgrade binutils.
> 
> I think that is fine, we just need to be able to make it easy for users for
> be doing the right thing.  i.e. a configure check that will really prevent

You can take a look at the testcases I added to binutils. They are
vers23, vers22 and vers21 in ld/testsuite/ld-elfvers.

> people from attempting to use the losing tools.  Hopefully we can see a
> future GNU binutils release relatively soon so that we can have a clear,
> canonical, and official GNU, best version to refer to.

I don't think you can count on that unless they make a release for
every Linux bug fixed, which is what I have been doing with my Linux
binutils.

H.J.

References:
- Re: problems with ctype...
  - From: H. J. Lu
- Re: problems with ctype...
  - From: Roland McGrath

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