From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] kernel compile problem
Date: Tue, 19 Dec 2006 17:49:11 +0100 [thread overview]
Message-ID: <20061219164911.GA18730@aon.at> (raw)
In-Reply-To: <Pine.LNX.4.64.0612191120350.31862@smtcorms05.samuelmanutech.com>
On Tue, Dec 19, 2006 at 11:22:01AM -0500, Robin Mordasiewicz wrote:
>On Fri, 15 Dec 2006, Robin Mordasiewicz wrote:
>
>> 2. I had to apply this kernel patch
>> http://www.kernel.org/pub/linux/devel/binutils/linux-2.6-seg-5.patch
>
>I see a kernel-patches directory. Is it possible to drop the kernel patch
>into that directory and have the ystem automatically patch the kernel, or
>is there another way of doing this automatically, or am I to manually
>apply the patch ?
I don't see why you would need that patch unless you'd use old binutils
or an anciant kernel.
If you think you need this patch, put it into that kernel-patches dir
and recompile, it'll get applied automagically.
next prev parent reply other threads:[~2006-12-19 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 20:14 [Buildroot] kernel compile problem Robin Mordasiewicz
2006-12-19 16:22 ` Robin Mordasiewicz
2006-12-19 16:49 ` Bernhard Fischer [this message]
2006-12-20 4:34 ` Robin Mordasiewicz
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=20061219164911.GA18730@aon.at \
--to=rep.nop@aon.at \
--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