From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: hppa glibc 2.3.3
Date: Thu, 7 Oct 2004 18:39:40 -0400 [thread overview]
Message-ID: <20041007223940.GM24430@baldric.uwo.ca> (raw)
In-Reply-To: <4161729B00001526@mail-1-bnl.tiscali.it>
> I look forward and encounter:
> <http://sources.redhat.com/ml/glibc-cvs/2004-q4/msg00074.html>
>
> It seems an evidence to just change errno to rtld_errno symbol for those
> other arch but for hppa I realy didn't encounter this variable name, what
> did I missed (certanly a macro but which one?)
Please please please, if you are going to quote other arches, read the
code before commenting.
i386 code is ancient and manipulates errno directly. We use the generic
code which is always kept up to date. Notice how alpha and ia64 didn't
need to be fixed? Neither do we :)
c.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-10-07 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409271755.i8RHtNoa017851@hiauly1.hia.nrc.ca>
[not found] ` <Pine.LNX.4.58.0409272134390.422@trillian.uni>
[not found] ` <20040928032200.GF27033@baldric.uwo.ca>
2004-09-28 8:52 ` [parisc-linux] Re: hppa glibc 2.3.3 experimental debs - patch Joel Soete
[not found] ` <Pine.LNX.4.58.0410050846320.924@trillian.uni>
2004-10-06 4:56 ` [parisc-linux] Re: hppa glibc 2.3.3 Carlos O'Donell
[not found] ` <4161729B00001345@mail-1-bnl.tiscali.it>
2004-10-07 15:29 ` Carlos O'Donell
2004-10-07 16:08 ` Joel Soete
2004-10-07 17:03 ` Joel Soete
2004-10-07 22:39 ` Carlos O'Donell [this message]
2004-10-08 6:00 Joel Soete
2004-10-08 17:01 ` Carlos O'Donell
2004-10-11 4:44 ` Randolph Chung
2004-10-12 20:38 ` Carlos O'Donell
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=20041007223940.GM24430@baldric.uwo.ca \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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