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 00:45:49 -0400 [thread overview]
Message-ID: <20021026044549.GA15461@nevyn.them.org> (raw)
In-Reply-To: <20021025164132.A23230@lucon.org>
On Fri, Oct 25, 2002 at 04:41:32PM -0700, H. J. Lu wrote:
> On Fri, Oct 25, 2002 at 04:36:58PM -0700, Roland McGrath wrote:
> > You know better than I what existing mips libc.so.6 ABIs have for the size
> > of sys_errlist. But for the current version, 123 omits many of the errno
> > values I see in asm-mips/errno.h, and EDQUOT really is 1133. So I don't
> > see how your change can be right.
>
> That is what was in glibc 2.0 for mips. However, glibc 2.2 is the first
> glibc version I worked on. I don't have any mips binaries compiled
> against glibc 2.0. As far as I know, none of glibc prior to the one
> with all my mips patches applied ever worked 100% correct on mips.
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
(That's 1134*4 in the new one and 123*4 in the older one). There's a
lot of these beasts deployed and I'd hate to see an incompatible change
now!
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-26 4:47 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 [this message]
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
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=20021026044549.GA15461@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