linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Help building compat-wireless
Date: Wed, 29 Feb 2012 08:43:56 -0700	[thread overview]
Message-ID: <4F4E47BC.8000306@mlbassoc.com> (raw)

I'm struggling a bit to build compat-wireless in a cross-build environment.
I normally don't build kernels in-tree, rather I use a build tree, e.g.
   % cd <linux-source>
   % mkdir /tmp/kernel_build
   % make O=/tmp/kernel_build <some_config>
   % make O=/tmp/kernel_build uImage

I can't see how to use this setup with the compat-wireless package.
I tried [all the combinations I could think of] something like this:
   % cd <compat-wireless>
   % make KLIB=<linux-source> KLIB_BUILD=/tmp/kernel_build
However, this seems to not work as all I get are errors like this:
   /local/compat-wireless-2012-02-28/config.mk:242: "WARNING: CONFIG_CFG80211_WEXT will be deactivated or not working because kernel was compiled with CONFIG_WIRELESS_EXT=n. Tools 
using wext interface like iwconfig will not work. To activate it build your kernel e.g. with CONFIG_LIBIPW=m."

Does this process work in my workflow?  What do I need to do to
get it going?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

             reply	other threads:[~2012-02-29 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 15:43 Gary Thomas [this message]
2012-02-29 18:48 ` Help building compat-wireless Gary Thomas
2012-02-29 19:44   ` Gary Thomas
2012-02-29 19:59     ` Thomas Pedersen
2012-02-29 20:18       ` Gary Thomas
2012-03-01  0:08         ` Thomas Pedersen
2012-03-01  6:08           ` Luciano Coelho

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=4F4E47BC.8000306@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --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).