The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: __NR_ia32_restart_syscall undeclared
Date: Thu, 26 May 2005 21:38:03 +0200	[thread overview]
Message-ID: <4296259B.50908@g-house.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

compiling 2.6.12-rc4 and 2.6.12-rc5-mm1 too on x86_64 breaks with:

  CC      arch/x86_64/kernel/process.o
  CC      arch/x86_64/kernel/semaphore.o
  CC      arch/x86_64/kernel/signal.o
arch/x86_64/kernel/signal.c: In function `do_signal':
arch/x86_64/kernel/signal.c:460: error: `__NR_ia32_restart_syscall'
undeclared (first use in this function)
arch/x86_64/kernel/signal.c:460: error: (Each undeclared identifier is
reported only once
arch/x86_64/kernel/signal.c:460: error: for each function it appears in.)
make[1]: *** [arch/x86_64/kernel/signal.o] Error 1
make: *** [arch/x86_64/kernel] Error 2


including asm/ia32_unistd.h helps, but i don't know if it is the
Right Thing to do.

thank you,
Christian.


- --- linux-2.6-git/arch/x86_64/kernel/signal.c.orig      2005-05-22
15:37:50.262209040 +0200
+++ linux-2.6-git/arch/x86_64/kernel/signal.c   2005-05-22
15:38:46.886600824 +0200
@@ -28,6 +28,7 @@
 #include <asm/uaccess.h>
 #include <asm/i387.h>
 #include <asm/proto.h>
+#include <asm/ia32_unistd.h>

 /* #define DEBUG_SIG 1 */


- --
BOFH excuse #214:

Fluorescent lights are generating negative ions. If turning them off
doesn't work, take them out and put tin foil on the ends.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCliWa+A7rjkF8z0wRApzdAJ9q8+nb6U5uMwYQMSqYULnmEg8QPwCfT7C3
4Zv2kIryVCyyU3OZIj/lszY=
=Q8xL
-----END PGP SIGNATURE-----

                 reply	other threads:[~2005-05-26 19:40 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=4296259B.50908@g-house.de \
    --to=evil@g-house.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox