Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Roland McGrath <roland@redhat.com>
Cc: Daniel Jacobowitz <dan@debian.org>,
	GNU C Library <libc-alpha@sources.redhat.com>,
	linux-mips@linux-mips.org
Subject: Re: PATCH: Fix errlist for mips
Date: Tue, 5 Nov 2002 19:23:28 -0800	[thread overview]
Message-ID: <20021105192328.A2230@lucon.org> (raw)
In-Reply-To: <200211060253.gA62rH817728@magilla.sf.frob.com>; from roland@redhat.com on Tue, Nov 05, 2002 at 06:53:17PM -0800

On Tue, Nov 05, 2002 at 06:53:17PM -0800, Roland McGrath wrote:
> > Here's what my MIPS glibc has:
> > 0019df30 g    DO .data  000001ec (GLIBC_2.0)  sys_errlist
> > 0019df30 g    DO .data  000011b8  GLIBC_2.2   sys_errlist
> > 0019df30 g    DO .data  000001ec (GLIBC_2.0)  _sys_errlist
> > 0019df30 g    DO .data  000011b8  GLIBC_2.2   _sys_errlist
> 
> Ok, that says sys_nerr=123 in 2.0 and sys_nerr=1134 in 2.2.
> I have changed the map to have just those.

Please keep in mind that the next version is GLIBC_2.1, not
GLIBC_2.2. The reason you see GLIBC_2.2 is GLIBC_2.2 is the
first versioned ABI for MIPS.


H.J.

  reply	other threads:[~2002-11-06  3:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021020172331.A26834@lucon.org>
2002-10-25 23:36 ` PATCH: Fix errlist for mips Roland McGrath
2002-10-25 23:41   ` H. J. Lu
2002-10-26  4:45     ` Daniel Jacobowitz
2002-10-26  4:55       ` H. J. Lu
2002-10-26 18:14         ` Daniel Jacobowitz
2002-10-26 18:20           ` H. J. Lu
2002-11-06  2:53           ` Roland McGrath
2002-11-06  3:23             ` H. J. Lu [this message]
2002-11-06  3:44               ` Roland McGrath
2002-11-06  3:53                 ` H. J. Lu
2002-11-06  4:05                   ` Roland McGrath
2002-11-06  4:14                     ` H. J. Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021105192328.A2230@lucon.org \
    --to=hjl@lucon.org \
    --cc=dan@debian.org \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=roland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox