public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [PATCH] IA32 support without sysctl doesn't work
Date: Sun, 02 Feb 2003 22:54:11 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805797@msgid-missing> (raw)

If you try to compile with CONFIG_IA32 on and CONFIG_SYSCTL off, then
you get an undefined reference to do_sysctl() on final link.

I believe that if sysctl is turned off, it should be off for IA32
processes as well as for IA64 processes.  Here's a patch:

=== arch/ia64/ia32/ia32_entry.S 1.18 vs edited ==--- 1.18/arch/ia64/ia32/ia32_entry.S	Mon Jan 13 11:07:06 2003
+++ edited/arch/ia64/ia32/ia32_entry.S	Mon Feb  3 09:49:48 2003
@@ -347,7 +347,11 @@
 	data8 sys32_writev
 	data8 sys_getsid
 	data8 sys_fdatasync
+#ifdef CONFIG_SYSCTL
 	data8 sys32_sysctl
+#else
+	data8 sys32_ni_syscall
+#endif
 	data8 sys_mlock		  /* 150 */
 	data8 sys_munlock
 	data8 sys_mlockall
=== arch/ia64/ia32/sys_ia32.c 1.43 vs edited ==--- 1.43/arch/ia64/ia32/sys_ia32.c	Tue Jan 28 10:44:14 2003
+++ edited/arch/ia64/ia32/sys_ia32.c	Mon Feb  3 09:48:39 2003
@@ -3148,6 +3148,7 @@
 
 extern asmlinkage long sys_sysctl(struct __sysctl_args *args);
 
+#ifdef CONFIG_SYSCTL
 asmlinkage long
 sys32_sysctl (struct sysctl32 *args)
 {
@@ -3189,6 +3190,7 @@
 
 	return ret;
 }
+#endif
 
 asmlinkage long
 sys32_newuname (struct new_utsname *name)


             reply	other threads:[~2003-02-02 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:54 Peter Chubb [this message]
2003-02-03 19:34 ` [Linux-ia64] [PATCH] IA32 support without sysctl doesn't work David Mosberger
2003-03-06 21:55 ` Bjorn Helgaas
2003-03-07  6:28 ` David Mosberger

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=marc-linux-ia64-105590709805797@msgid-missing \
    --to=peter@chubb.wattle.id.au \
    --cc=linux-ia64@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