From: Ralf Baechle <ralf@oss.sgi.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Mike Klar <mfklar@ponymail.com>,
linux-mips@oss.sgi.com, linux-mips@fnet.fr,
linux-mips@vger.rutgers.edu
Subject: Re: errno assignment in _syscall macros and glibc
Date: Sun, 25 Jun 2000 23:59:17 +0200 [thread overview]
Message-ID: <20000625235917.C3802@bacchus.dhis.org> (raw)
In-Reply-To: <u8zoo9mw2d.fsf@gromit.rhein-neckar.de>; from aj@suse.de on Sun, Jun 25, 2000 at 08:53:30PM +0200
On Sun, Jun 25, 2000 at 08:53:30PM +0200, Andreas Jaeger wrote:
> I'm considering to commit the appended patch. I've compiled glibc
> with it and didn't notice any problems. If nobody objects, I'll apply
> it tomorrow.
>
> Ralf, are there any other places that needs to be changed?
libc/sysdeps/unix/sysv/linux/sys/syscall.h should be patched the same way.
I remember that I once saw a program the __NR_ syscall numbers imported
via unistd.h. Fixing won't be a big deal.
> What do you think of adding
> #ifdef KERNEL
> around _syscallX in <asm/unistd.h> ?
__KERNEL__ that is ...
Slightly radical but I like it. It'll break some programs which are using
the _syscallX() macros to get syscalls which libc doesn't yet have wrappers
for just to get away without fixing / upgrading libc. Those people still
can use syscall(3) in such a case.
Ralf
next prev parent reply other threads:[~2000-06-25 22:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NDBBIDGAOKMNJNDAHDDMCEODCKAA.mfklar@ponymail.com>
[not found] ` <u8d7l6p0vq.fsf@gromit.rhein-neckar.de>
2000-06-25 18:43 ` errno assignment in _syscall macros and glibc Ralf Baechle
2000-06-25 18:53 ` Andreas Jaeger
2000-06-25 21:59 ` Ralf Baechle [this message]
2000-06-25 19:26 ` Alan Cox
2000-06-25 19:26 ` Alan Cox
2000-06-25 21:21 ` Ralf Baechle
2000-06-25 21:25 ` Alan Cox
2000-06-25 21:25 ` Alan Cox
2000-06-25 21:48 ` Ralf Baechle
2000-06-30 14:03 ` Jay Carlson
2000-06-30 14:03 ` Jay Carlson
2000-07-03 13:45 ` Alan Cox
2000-07-03 13:45 ` Alan Cox
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=20000625235917.C3802@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=aj@suse.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=linux-mips@vger.rutgers.edu \
--cc=mfklar@ponymail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.