From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] missing kernel headers when compiling kismet
Date: Tue, 08 Dec 2009 23:09:53 +0100 [thread overview]
Message-ID: <873a3lnmmm.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <F9A30328-AECD-494A-A1BB-D28339481F10@hsr.ch> (Marc Egli's message of "Tue, 8 Dec 2009 22:27:08 +0100")
>>>>> "Marc" == Marc Egli <marc.egli@hsr.ch> writes:
Marc> make clean and make did result in the same error i got before:
Marc> checking for linux/wireless.h... (cached) no
Marc> find ./ -name wireless.h gave me:
Marc> ./output/toolchain/linux-2.6.31.6/include/linux/wireless.h
Marc> ./output/toolchain/uClibc_dev/usr/include/linux/wireless.h
Marc> ./output/toolchain/linux/include/linux/wireless.h
Marc> ./output/build/staging_dir/usr/include/linux/wireless.h
Marc> ./output/build/linux-2.6.31.6/include/config/wireless.h
Marc> ./output/build/linux-2.6.31.6/include/linux/wireless.h
Marc> ./output/build/ifplugd-0.28/src/wireless.h
Marc> and my config is attached
Hmm, I don't see any issues here with building the network packages you
had enabled (the most obvious ones to check for linux/wireless.h). I see
you have some local lxde packages enabled, maybe one of those checks for
wireless? Could you try temporarily disabling them and doing a clean
rebuild?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-12-08 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 20:28 [Buildroot] missing kernel headers when compiling kismet Marc Egli
2009-12-08 9:01 ` Peter Korsgaard
2009-12-08 10:25 ` Marc Egli
2009-12-08 12:55 ` Peter Korsgaard
2009-12-08 21:27 ` Marc Egli
2009-12-08 21:39 ` Marc Egli
2009-12-08 22:09 ` Peter Korsgaard [this message]
2009-12-09 8:33 ` Marc Egli
2009-12-09 13:21 ` Peter Korsgaard
2009-12-09 20:24 ` Marc Egli
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=873a3lnmmm.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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