From: Paul Larson <plars@linuxtestproject.org>
To: Werner Almesberger <wa@almesberger.net>
Cc: Andi Kleen <ak@suse.de>, Robert Williamson <robbiew@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
aniruddha.marathe@wipro.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Re: Same syscall is defined to different numbers on 3 different archs(was Re: Makefile issue)
Date: 08 Apr 2003 08:30:50 -0500 [thread overview]
Message-ID: <1049808651.30732.113.camel@plars> (raw)
In-Reply-To: <20030407232302.D19288@almesberger.net>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Mon, 2003-04-07 at 21:23, Werner Almesberger wrote:
> Andi Kleen wrote:
> > #include </path/to/kernel/source/include/asm-<arch>/unistd.h>
> > (you need the version in the kernel source because many glibc packagers
> > in their infinite wisdom use an old outdated copy of asm/ usually from
> > the last stable kernel only)
>
> Do we need a /proc/syscalls ? :-)
I don't think so. Apps should be accessing things through libraries
anyway. The only reason we don't in some cases like this is that it's
new and not in libs on any distro yet. Besides, I don't think having a
/proc/syscalls would be any better than having to do ifdefs or use
kernel headers.
-Paul Larson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-04-08 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF51DE965A.FDCB6DBE-ON85256D01.005201B1-86256D01.005610CF@pok.ibm.com.suse.lists.linux.kernel>
2003-04-07 15:54 ` Same syscall is defined to different numbers on 3 different archs(was Re: Makefile issue) Andi Kleen
2003-04-07 16:26 ` Robert Williamson
2003-04-07 18:08 ` David Mosberger
2003-04-07 18:16 ` Robert Williamson
2003-04-07 18:49 ` David Mosberger
2003-04-08 2:23 ` Werner Almesberger
2003-04-08 13:30 ` Paul Larson [this message]
2003-04-08 19:47 ` [LTP] " Werner Almesberger
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=1049808651.30732.113.camel@plars \
--to=plars@linuxtestproject.org \
--cc=ak@suse.de \
--cc=aniruddha.marathe@wipro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=robbiew@us.ibm.com \
--cc=wa@almesberger.net \
/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