From: Christoph Hellwig <hch@infradead.org>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: sparc64: ERROR: "sys_ioctl" [arch/sparc64/solaris/solaris.ko] undefined!
Date: Fri, 20 Jul 2007 16:11:54 +0000 [thread overview]
Message-ID: <20070720161154.GA17382@infradead.org> (raw)
In-Reply-To: <7157.1184937882@laptop13.inf.utfsm.cl>
On Fri, Jul 20, 2007 at 09:24:42AM -0400, Horst H. von Brand wrote:
> When building v2.6.22-3478-g275afca on sparc64 (.config attached) I get:
>
> MODPOST vmlinux
> Building modules, stage 2.
> MODPOST 463 modules
> ERROR: "sys_ioctl" [arch/sparc64/solaris/solaris.ko] undefined!
Sorry, my fault.
It looked to me like sparc64 exports sys_ioctl on it's own, but it only
exports compat_sys_ioctl on it's own.
Here's the fix:
Index: linux-2.6/arch/sparc64/kernel/sparc64_ksyms.c
=================================--- linux-2.6.orig/arch/sparc64/kernel/sparc64_ksyms.c 2007-07-20 17:09:25.000000000 +0200
+++ linux-2.6/arch/sparc64/kernel/sparc64_ksyms.c 2007-07-20 17:09:33.000000000 +0200
@@ -280,6 +280,7 @@ EXPORT_SYMBOL(sys_getgid);
EXPORT_SYMBOL(svr4_getcontext);
EXPORT_SYMBOL(svr4_setcontext);
EXPORT_SYMBOL(compat_sys_ioctl);
+EXPORT_SYMBOL(sys_ioctl);
EXPORT_SYMBOL(sparc32_open);
#endif
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: sparc64: ERROR: "sys_ioctl" [arch/sparc64/solaris/solaris.ko] undefined!
Date: Fri, 20 Jul 2007 17:11:54 +0100 [thread overview]
Message-ID: <20070720161154.GA17382@infradead.org> (raw)
In-Reply-To: <7157.1184937882@laptop13.inf.utfsm.cl>
On Fri, Jul 20, 2007 at 09:24:42AM -0400, Horst H. von Brand wrote:
> When building v2.6.22-3478-g275afca on sparc64 (.config attached) I get:
>
> MODPOST vmlinux
> Building modules, stage 2.
> MODPOST 463 modules
> ERROR: "sys_ioctl" [arch/sparc64/solaris/solaris.ko] undefined!
Sorry, my fault.
It looked to me like sparc64 exports sys_ioctl on it's own, but it only
exports compat_sys_ioctl on it's own.
Here's the fix:
Index: linux-2.6/arch/sparc64/kernel/sparc64_ksyms.c
===================================================================
--- linux-2.6.orig/arch/sparc64/kernel/sparc64_ksyms.c 2007-07-20 17:09:25.000000000 +0200
+++ linux-2.6/arch/sparc64/kernel/sparc64_ksyms.c 2007-07-20 17:09:33.000000000 +0200
@@ -280,6 +280,7 @@ EXPORT_SYMBOL(sys_getgid);
EXPORT_SYMBOL(svr4_getcontext);
EXPORT_SYMBOL(svr4_setcontext);
EXPORT_SYMBOL(compat_sys_ioctl);
+EXPORT_SYMBOL(sys_ioctl);
EXPORT_SYMBOL(sparc32_open);
#endif
next prev parent reply other threads:[~2007-07-20 16:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 13:24 sparc64: ERROR: "sys_ioctl" [arch/sparc64/solaris/solaris.ko] undefined! Horst H. von Brand
2007-07-20 13:24 ` Horst H. von Brand
2007-07-20 16:11 ` Christoph Hellwig [this message]
2007-07-20 16:11 ` Christoph Hellwig
2007-07-22 2:22 ` sparc64: ERROR: "sys_ioctl" [arch/sparc64/solaris/solaris.ko] David Miller
2007-07-22 2:22 ` sparc64: ERROR: "sys_ioctl" [arch/sparc64/solaris/solaris.ko] undefined! David Miller
2007-07-22 5:43 ` [RFC] Kconfig fun with sparc32/sparc64 rtc drivers Al Viro
2007-07-22 5:43 ` Al Viro
2007-07-22 5:54 ` David Miller
2007-07-22 5:54 ` David Miller
2007-07-22 6:19 ` Al Viro
2007-07-22 6:19 ` Al Viro
2007-07-22 6:22 ` David Miller
2007-07-22 6:22 ` David Miller
2007-07-22 6:31 ` Al Viro
2007-07-22 6:31 ` Al Viro
2007-07-22 6:35 ` Al Viro
2007-07-22 6:35 ` Al Viro
2007-07-22 6:39 ` David Miller
2007-07-22 6:39 ` David Miller
2007-07-22 7:22 ` Al Viro
2007-07-22 7:22 ` Al Viro
2007-07-22 7:26 ` [PATCH] sparc32 missing exports Al Viro
2007-07-22 7:26 ` Al Viro
2007-07-22 7:38 ` David Miller
2007-07-22 7:38 ` David Miller
2007-07-22 7:37 ` [RFC] Kconfig fun with sparc32/sparc64 rtc drivers David Miller
2007-07-22 7:37 ` David Miller
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=20070720161154.GA17382@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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.