From: Adrian Bunk <bunk@fs.tum.de>
To: golbi@mat.uni.torun.pl, wrona@mat.uni.torun.pl
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] POSIX_MQUEUE depends on NET
Date: Sat, 29 May 2004 15:01:02 +0200 [thread overview]
Message-ID: <20040529130102.GO16099@fs.tum.de> (raw)
POSIX_MQUEUE=y and NET=n results in the following compile error in
2.6.7-mm1:
<-- snip -->
...
LD .tmp_vmlinux1
ipc/built-in.o(.text+0x50fd): In function `__do_notify':
: undefined reference to `netlink_sendskb'
ipc/built-in.o(.text+0x52a1): In function `remove_notification':
: undefined reference to `netlink_sendskb'
ipc/built-in.o(.text+0x5c23): In function `sys_mq_notify':
: undefined reference to `netlink_detachskb'
ipc/built-in.o(.text+0x5c50): In function `sys_mq_notify':
: undefined reference to `__kfree_skb'
ipc/built-in.o(.text+0x5d34): In function `sys_mq_notify':
: undefined reference to `alloc_skb'
ipc/built-in.o(.text+0x5da9): In function `sys_mq_notify':
: undefined reference to `netlink_getsockbyfilp'
ipc/built-in.o(.text+0x5dd6): In function `sys_mq_notify':
: undefined reference to `netlink_attachskb'
ipc/built-in.o(.text+0x5dfb): In function `sys_mq_notify':
: undefined reference to `skb_over_panic'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
The fix is simple:
--- linux-2.6.7-rc1-mm1-full/init/Kconfig.old 2004-05-29 14:39:13.000000000 +0200
+++ linux-2.6.7-rc1-mm1-full/init/Kconfig 2004-05-29 14:39:25.000000000 +0200
@@ -92,7 +92,7 @@
config POSIX_MQUEUE
bool "POSIX Message Queues"
- depends on EXPERIMENTAL
+ depends on NET && EXPERIMENTAL
---help---
POSIX variant of message queues is a part of IPC. In POSIX message
queues every message has a priority which decides about succession
Please apply
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
reply other threads:[~2004-05-29 13:01 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=20040529130102.GO16099@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=golbi@mat.uni.torun.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=wrona@mat.uni.torun.pl \
/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
all inboxes | Powered by JetHome®