From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, jbenc@suse.cz
Subject: Re: mac80211: build failure if enabled - 2.6.22 vanilla
Date: Tue, 10 Jul 2007 12:22:58 -0700 [thread overview]
Message-ID: <4693DC92.2010209@intel.com> (raw)
In-Reply-To: <4693DBD4.5010903@lwfinger.net>
Larry Finger wrote:
> Kok, Auke wrote:
>> I realize mac80211 isn't really helpfull if you don't build any drivers
>> that use it, but I currently get:
>>
>> ...
>> CC [M] drivers/scsi/ch.o
>> LD [M] net/llc/llc.o
>> LD net/mac80211/built-in.o
>> make[2]: *** No rule to make target `net/mac80211/ieee80211.o', needed
>> by `net/mac80211/mac80211.o'. Stop.
>> make[2]: *** Waiting for unfinished jobs....
>> make[1]: *** [net/mac80211] Error 2
>> make: *** [net] Error 2
>> make: *** Waiting for unfinished jobs....
>>
>> if I enable CONFIG_MAC80211=m without selecting any drivers that use
>> this subsystem.
>
> There is something funny here. I just built a 2.6.22 system with mac80211 without any drivers that
> use it, and everything worked OK. This was on an X86_64 system. What is your architecture?
32-bit... I'm trying now with a clean kernel and all and will post the .config
in a bit (that's if I can reproduce... I was mucking with my tree to get iwl to
compile and blew some changes).
Auke
prev parent reply other threads:[~2007-07-10 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 18:55 mac80211: build failure if enabled - 2.6.22 vanilla Kok, Auke
2007-07-10 19:13 ` Jiri Benc
2007-07-10 20:06 ` Kok, Auke
2007-07-10 19:19 ` Larry Finger
2007-07-10 19:22 ` Kok, Auke [this message]
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=4693DC92.2010209@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=jbenc@suse.cz \
--cc=larry.finger@lwfinger.net \
--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;
as well as URLs for NNTP newsgroup(s).