From: Evgeniy Polyakov <zbr@ioremap.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeff Garzik <jgarzik@pobox.com>, Zhu Yi <yi.zhu@intel.com>,
James Ketrenos <jketreno@linux.intel.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: ieee80211_crypt_wep.c:(.text+0x90dd7): undefined reference to `crypto_free_tfm'
Date: Sat, 8 Nov 2008 13:13:30 +0300 [thread overview]
Message-ID: <20081108101330.GA19184@ioremap.net> (raw)
In-Reply-To: <20081108075437.GA312@elte.hu>
Hi Ingo.
On Sat, Nov 08, 2008 at 08:54:37AM +0100, Ingo Molnar (mingo@elte.hu) wrote:
> not sure whether this has been reported before, but with latest upstream
> i get this new build failure with certain (rare, randconfig) configs:
>
> net/built-in.o: In function `prism2_wep_deinit':
> ieee80211_crypt_wep.c:(.text+0x90dd7): undefined reference to `crypto_free_tfm'
> ieee80211_crypt_wep.c:(.text+0x90de3): undefined reference to `crypto_free_tfm'
> net/built-in.o: In function `prism2_wep_init':
> ieee80211_crypt_wep.c:(.text+0x90fab): undefined reference to `crypto_alloc_base'
> ieee80211_crypt_wep.c:(.text+0x90fc9): undefined reference to `crypto_alloc_base'
> ieee80211_crypt_wep.c:(.text+0x91007): undefined reference to `crypto_free_tfm'
> ieee80211_crypt_wep.c:(.text+0x91031): undefined reference to `crypto_free_tfm'
The problem is:
> CONFIG_IEEE80211=y
> CONFIG_IEEE80211_CRYPT_WEP=y
> CONFIG_CRYPTO=m
While
config IEEE80211_CRYPT_WEP
tristate "IEEE 802.11 WEP encryption (802.1x)"
depends on IEEE80211
select CRYPTO
Looks like select does not force 'yes' instead of 'module'?
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-11-08 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 7:54 ieee80211_crypt_wep.c:(.text+0x90dd7): undefined reference to `crypto_free_tfm' Ingo Molnar
2008-11-08 10:13 ` Evgeniy Polyakov [this message]
2008-11-09 9:10 ` David Shwatrz
2008-11-10 8:33 ` Ingo Molnar
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=20081108101330.GA19184@ioremap.net \
--to=zbr@ioremap.net \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.intel.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.com \
/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.