From: Daniel Jacobowitz <dan@debian.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Roland McGrath <roland@redhat.com>,
GNU C Library <libc-alpha@sources.redhat.com>,
linux-mips@linux-mips.org
Subject: Re: PATCH: Fix errlist for mips
Date: Sat, 26 Oct 2002 14:14:31 -0400 [thread overview]
Message-ID: <20021026181431.GA11105@nevyn.them.org> (raw)
In-Reply-To: <20021025215543.A26333@lucon.org>
On Fri, Oct 25, 2002 at 09:55:43PM -0700, H. J. Lu wrote:
> On Sat, Oct 26, 2002 at 12:45:49AM -0400, Daniel Jacobowitz wrote:
> > Not everyone uses your MIPS patches; I have a completely functional
> > MIPS system with:
> > 0019df30 l O .data 000011b8 _new_sys_errlist
> > 0019df30 l O .data 000001ec _old_sys_errlist
>
> It doesn't tell anything. Please, please show size of sys_errlist in
> glibc 2.0 for mips. I am not even sure if you can run mips binaries
> compiled against glibc 2.0 with glibc 2.2/2.3.
I didn't use 2.0 for MIPS either. And I got the wrong impression from
your last message; sorry!
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
So: I don't know where the GLIBC_2.1 version came from, or why we need
a GLIBC_2.3 version, or why we should change the size of the GLIBC_2.0
version. Your patch looks good; should you wipe the GLIBC_2.1 version
also?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-26 18:14 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 [this message]
2002-10-26 18:20 ` H. J. Lu
2002-11-06 2:53 ` Roland McGrath
2002-11-06 3:23 ` H. J. Lu
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=20021026181431.GA11105@nevyn.them.org \
--to=dan@debian.org \
--cc=hjl@lucon.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