From: Andreas Mohr <andi@lisas.de>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: BUG: build fail due to dependency issue (LIB80211_CRYPT_* failed to depend on LIB80211)
Date: Mon, 6 Jan 2014 15:01:03 +0100 [thread overview]
Message-ID: <20140106140103.GA24241@rhlx01.hs-esslingen.de> (raw)
Hi,
just had the following non-satisfactory build result here
(read: caused sizeable waste of time):
SORTEX vmlinux
SYSMAP System.map
Building modules, stage 2.
MODPOST 210 modules
ERROR: "lib80211_unregister_crypto_ops" [net/wireless/lib80211_crypt_wep.ko] undefined!
ERROR: "lib80211_register_crypto_ops" [net/wireless/lib80211_crypt_wep.ko] undefined!
ERROR: "lib80211_unregister_crypto_ops" [net/wireless/lib80211_crypt_tkip.ko] undefined!
ERROR: "lib80211_register_crypto_ops" [net/wireless/lib80211_crypt_tkip.ko] undefined!
ERROR: "lib80211_unregister_crypto_ops" [net/wireless/lib80211_crypt_ccmp.ko] undefined!
ERROR: "lib80211_register_crypto_ops" [net/wireless/lib80211_crypt_ccmp.ko] undefined!
make[5]: *** [__modpost] Error 1
make[4]: *** [modules] Error 2
This is due to net/wireless/Kconfig:
config LIB80211
tristate
default n
help
This options enables a library of common routines used
by IEEE802.11 wireless LAN drivers.
Drivers should select this themselves if needed.
config LIB80211_CRYPT_WEP
tristate
config LIB80211_CRYPT_CCMP
tristate
config LIB80211_CRYPT_TKIP
tristate
config LIB80211_DEBUG
bool "lib80211 debugging messages"
depends on LIB80211
default n
---help---
You can enable this if you want verbose debugging messages
from lib80211.
A
make menuconfig
showed these three crypt options rather very prominently,
yet with entry of LIB80211 proper nowhere to be seen,
thus it was very easy to fall into the trap of "enabling"
various crypto options, thereby "enabling" nice ultimate build failure.
And as you can see above as well, LIB80211_DEBUG decided to be
a law-abiding citizen, by caring to announce a proper dependency on LIB80211.
Happened on OpenWrt's 3.10.24, and verified Kconfig status to still be identical on linux trunk.
Thanks,
Andreas Mohr
--
GNU/Linux. It's not the software that's free, it's you.
next reply other threads:[~2014-01-06 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 14:01 Andreas Mohr [this message]
2014-01-06 14:09 ` Johannes Berg
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=20140106140103.GA24241@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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
all inboxes | Powered by JetHome®