From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Balaji Ravindran <b@w1an.in>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: Question on general wireless testing tree compilation.
Date: Fri, 25 Sep 2009 08:58:58 +0200 [thread overview]
Message-ID: <200909250858.58989.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <16D9C5FD-4A2A-4061-9C26-FF5C0B0CDFBA@w1an.in>
> I followed the instructions from
> http://www.cyberciti.biz/tips/compiling-linux-kernel-26.html
> and ended up with a compile error in 'make', while trying to
> create the bzimage. (error is on make: initramfs_data.cpi.o
> failed)
Hmm, I simply compile almost-self-contained kernels, without any
initramfs. Slows down the boot and isn't needed for the usual
IDE/SATA desktop PCs anyway.
If you don't want to go that way, you'd better post the whole
error. Maybe when doing "make V=1", and include some (10 or so)
lines from above the error message above.
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2009-09-25 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 5:21 Question on general wireless testing tree compilation Balaji Ravindran
2009-09-25 6:58 ` Holger Schurig [this message]
2009-09-28 21:52 ` Hin-Tak Leung
2009-09-29 7:29 ` Balaji Ravindran
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=200909250858.58989.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=b@w1an.in \
--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