From: Mathieu Chouquet-Stringer <mchouque@online.fr>
To: sparclinux@vger.kernel.org
Subject: unistd.h: warning: conflicting types for built-in function '_exit'
Date: Wed, 12 May 2004 00:23:03 +0000 [thread overview]
Message-ID: <20040512002303.GA25190@localhost> (raw)
Hi all,
I was trying to compile the latest 2.6 bk with gcc 3.4.0 and came across
this error. I checked the history of include/asm-i386/unistd.h and Andrew Morton
removed 2 lines in revision 1.32.
Here's his comment:
"Just remove the dang thing - nobody uses _exit().
Except for the vmware stub, which breaks. So I kindly exported do_exit() to
kernel modules, just for vmware..."
Because vmware is only a i386 thing, I guess we don't need to do this so I
just replicated his work for sparc64.
Let me know if this is correct.
Cheers
--- include/asm-sparc64/unistd.h.orig 2004-05-11 20:05:11.000000000 -0400
+++ include/asm-sparc64/unistd.h 2004-05-11 20:06:58.000000000 -0400
@@ -437,7 +437,7 @@
* won't be any messing with the stack from main(), but we define
* some others too.
*/
-#define __NR__exit __NR_exit
+
static __inline__ _syscall0(pid_t,setsid)
static __inline__ _syscall3(int,write,int,fd,__const__ char *,buf,off_t,count)
static __inline__ _syscall3(int,read,int,fd,char *,buf,off_t,count)
@@ -446,7 +446,7 @@
static __inline__ _syscall3(int,execve,__const__ char *,file,char **,argv,char **,envp)
static __inline__ _syscall3(int,open,__const__ char *,file,int,flag,int,mode)
static __inline__ _syscall1(int,close,int,fd)
-static __inline__ _syscall1(int,_exit,int,exitcode)
+
static __inline__ _syscall3(pid_t,waitpid,pid_t,pid,int *,wait_stat,int,options)
#include <linux/linkage.h>
--
Mathieu Chouquet-Stringer E-Mail: mchouque@online.fr
Never attribute to malice that which can be adequately
explained by stupidity.
-- Hanlon's Razor --
reply other threads:[~2004-05-12 0:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040512002303.GA25190@localhost \
--to=mchouque@online.fr \
--cc=sparclinux@vger.kernel.org \
/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.