From: Brian Haley <brian.haley@hp.com>
To: johannes@sipsolutions.net
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Can't build net-next-2.6 without CONFIG_MAC80211_MESH
Date: Tue, 30 Sep 2008 10:35:54 -0400 [thread overview]
Message-ID: <48E2394A.3010707@hp.com> (raw)
Sorry if this has been discussed/fixed already, but I just noticed last
night I couldn't build net-next-2.6:
Kernel: arch/x86/boot/bzImage is ready (#71)
ERROR: "mpp_path_lookup" [net/mac80211/mac80211.ko] undefined!
ERROR: "mpp_path_add" [net/mac80211/mac80211.ko] undefined!
These are defined in net/mac80211/mesh_pathtbl.c, but being called from
rx.c and tx.c, but I'm not building the mesh files:
--> grep CONFIG_MAC80211 .config
CONFIG_MAC80211=m
CONFIG_MAC80211_RC_PID=y
CONFIG_MAC80211_RC_DEFAULT_PID=y
CONFIG_MAC80211_RC_DEFAULT="pid"
# CONFIG_MAC80211_MESH is not set
# CONFIG_MAC80211_LEDS is not set
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
make oldconfig didn't make any changes, so I think the config is valid.
-Brian
next reply other threads:[~2008-09-30 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 14:35 Brian Haley [this message]
2008-09-30 14:43 ` Can't build net-next-2.6 without CONFIG_MAC80211_MESH John W. Linville
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=48E2394A.3010707@hp.com \
--to=brian.haley@hp.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).