From: Michael Buesch <mb@bu3sch.de>
To: sHittmeyer <hittmeyer@corscience.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: building compat-wireless-2.6
Date: Fri, 29 Aug 2008 13:20:21 +0200 [thread overview]
Message-ID: <200808291320.22188.mb@bu3sch.de> (raw)
In-Reply-To: <48B7B84F.9030709@corscience.de>
On Friday 29 August 2008, sHittmeyer wrote:
> Hello,
> I just copied the actual git repository of compat-wireless-2.6 and wa=
nt=20
> to compile it for a kernel 2.6.23 which is patched for a =B5C so im f=
ixed=20
> on that Kernel.
>=20
> I changed the Makefile so I can Cross_Compile the compat-wireless-2.6=
=20
> for that Kernel but in the Makefile there is a script used before=20
> compile which checks and inits the config. The problem is, it doesn't=
=20
> work. I immediately get the message:
> =20
> ---> cat: /home/stefan/compat-wireless-2.6/compat-release: No such fi=
le=20
> or directory
> ---> cat: /home/stefan/compat-wireless-2.6/compat-release: No such fi=
le=20
> or directory
> ./scripts/gen-compat-autoconf.sh config.mk >=20
> include/linux/compat_autoconf.h
> ./scripts/check_config.sh: line 12:=20
> include/linux/compat_autoconf.h: No such file or directory
> cat: /home/stefan/compat-wireless-2.6/compat-release: No such f=
ile=20
> or directory
I guess you need to install your kernel sourcecode.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-08-29 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 8:50 building compat-wireless-2.6 sHittmeyer
2008-08-29 11:20 ` Michael Buesch [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=200808291320.22188.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=hittmeyer@corscience.de \
--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).