[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <12c511ca0705071529w38f71b09je0d9b460c7bc3025@mail.gmail.com>
Date: Mon, 7 May 2007 15:29:52 -0700
From: "Tony Luck" <tony.luck@...el.com>
To: "Sam Ravnborg" <sam@...nborg.org>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Kees Cook" <kees@...flux.net>,
"Randy Dunlap" <randy.dunlap@...cle.com>,
linux-kernel@...r.kernel.org,
"David Woodhouse" <dwmw2@...radead.org>
Subject: Re: [PATCH 1/3] kbuild: complain about missing system calls.
On 3/21/07, Sam Ravnborg <sam@...nborg.org> wrote:
> Most system calls seem to get added to i386 first. This patch
> automatically generates a warning for any new system call which is
> implemented on i386 but not the architecture currently being compiled.
This is now upstream, and so I see a bunch of warnings for every ia64
build. Some of them are real, I need to add some syscalls, but there
are a few bogus ones because ia64 chose different names (e.g. we have
a sys_clone() that glibc uses to implement fork() and vfork()).
Just checking that the right way for me to shut checksyscalls.sh up is
to add:
#define __IGNORE_fork
#define __IGNORE_vfork
etc. to include/asm-ia64/unistd.h for each of the bogus ones. Or is there
some other preferred mechanism?
-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists