Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Building compat-wireless from 2.6.27
Date: Fri, 22 Jan 2010 11:21:17 -0800	[thread overview]
Message-ID: <4B59FAAD.6060804@redfish-solutions.com> (raw)

I'm trying to build compat-wireless's snapshot from git on compat-wireless-2.6-mcgrof last night, on linux 2.6.27.42 and getting:

...
make -j5 -C /home/philipp/alix/build_i586/compat-wireless-2010-01-21 \
		HOSTCC=gcc CC=/home/philipp/alix/build_i586/staging_dir/bin/i586-linux-uclibc-gcc ARCH=i386 \
		KLIB_BUILD=/home/philipp/alix/build_i586/linux-2.6.27.42-astlinux \
		MODPROBE='true' PWD=/home/philipp/alix/build_i586/compat-wireless-2010-01-21 \
		CONFIG_IPW2100= CONFIG_IPW2200= CONFIG_LIBERTAS= CONFIG_B44= CONFIG_B43= CONFIG_B43LEGACY= \
		modules
make[1]: Entering directory `/home/philipp/alix/build_i586/compat-wireless-2010-01-21'
./scripts/gen-compat-autoconf.sh config.mk > include/linux/compat_autoconf.h
make[2]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
make -C /home/philipp/alix/build_i586/linux-2.6.27.42-astlinux M=/home/philipp/alix/build_i586/compat-wireless-2010-01-21 modules
make[2]: Entering directory `/home/philipp/alix/build_i586/linux-2.6.27.42-astlinux'
scripts/Makefile.build:41: /home/philipp/alix/build_i586/compat-wireless-2010-01-21/compat/Makefile: No such file or directory
make[4]: *** No rule to make target `/home/philipp/alix/build_i586/compat-wireless-2010-01-21/compat/Makefile'.  Stop.
make[3]: *** [/home/philipp/alix/build_i586/compat-wireless-2010-01-21/compat] Error 2
make[3]: *** Waiting for unfinished jobs....
scripts/Makefile.build:41: /home/philipp/alix/build_i586/compat-wireless-2010-01-21/drivers/bluetooth/Makefile: No such file or directory
make[4]: *** No rule to make target `/home/philipp/alix/build_i586/compat-wireless-2010-01-21/drivers/bluetooth/Makefile'.  Stop.
make[3]: *** [/home/philipp/alix/build_i586/compat-wireless-2010-01-21/drivers/bluetooth] Error 2
make[2]: *** [_module_/home/philipp/alix/build_i586/compat-wireless-2010-01-21] Error 2
make[2]: Leaving directory `/home/philipp/alix/build_i586/linux-2.6.27.42-astlinux'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/philipp/alix/build_i586/compat-wireless-2010-01-21'
make: *** [/home/philipp/alix/build_i586/compat-wireless-2010-01-21/net/wireless/lib80211.ko] Error 2
% 

as a diagnostic, I've patched my makefile to $(info ...) out the following:

CONFIG_PCI=y
CONFIG_USB=y
CONFIG_PCMCIA=
CONFIG_SSB=
CONFIG_LIBERTAS=
CONFIG_ATH5K=m
CONFIG_ATH9K=m
CONFIG_IPW2100=
CONFIG_IPW2200=
CONFIG_IWLWIFI=m
CONFIG_B43=
CONFIG_B43LEGACY=
CONFIG_B44=


How should I be building compat-wireless?  This worked until about early December.

-Philip



             reply	other threads:[~2010-01-22 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 19:21 Philip A. Prindeville [this message]
2010-01-22 19:48 ` Building compat-wireless from 2.6.27 Luis R. Rodriguez

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=4B59FAAD.6060804@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox