From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel Download Error with external toolchain
Date: Fri, 28 Sep 2007 22:58:33 +0200 [thread overview]
Message-ID: <20070928205833.GA20951@aon.at> (raw)
In-Reply-To: <1191012546.6616.15.camel@venture.bit63.org>
On Fri, Sep 28, 2007 at 04:49:06PM -0400, Clark Rawlins wrote:
>On Fri, 2007-09-28 at 21:16 +0200, Bernhard Fischer wrote:
>> On Fri, Sep 28, 2007 at 09:01:57PM +0200, Ulf Samuelsson wrote:
>> >fre 2007-09-28 klockan 20:08 +0200 skrev Bernhard Fischer:
>> >> On Fri, Sep 28, 2007 at 09:18:26AM -0400, Clark Rawlins wrote:
>> >> >When attempting to build a fairly simple config including a kernel using
>> >> >an external toolchain I am getting the following error:
>> >> >
>> >> >http://www.kernel.org/pub/linux/kernel/v2.6//linux-...tar.bz2
>>
>> >Give time to do development, without beeing to intrusive.
>> >
>> >Been tied down with other stuff so It has not gotten
>> >the attention it deserved.
>>
>> np. It wouldn't have really helped either way without a little love..
>> Compiling a kernel with his external toolchain and setting the
>> INST_MOD_PATH properly shouldn't be that hard.
>
>True, It is easy enough, I just hopped (based on the configuration
>options) that this was supported.
>
>Here is the patch I am using to accomplish this. It seems like it may
>be a bit of a hack, but I couldn't see a better way to do it without
>really diving in, so I am open to suggestions.
Well, it shouldn't be depending on the external stuff.
There should be a knob that is settable in Config to set if
kernel-headers-version == kernel-src-version (for TOOLCHAIN_SOURCE)
or not. If not or if TOOLCHAIN_EXTERNAL then use the given kernel-src-version
for building the kernel, keep using the kernel-headers-version for
headers-install (including unpacking, patching, etc. Both will need
this if kernel-headers-version != kernel-src-version, of course).
I'm just using the == case, so help with the other case is welcome
(including non-2.6 kernel-src, as some will most likely demand..)
cheers and TIA,
next prev parent reply other threads:[~2007-09-28 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 13:18 [Buildroot] Kernel Download Error with external toolchain Clark Rawlins
2007-09-28 18:08 ` Bernhard Fischer
2007-09-28 18:16 ` Clark Rawlins
2007-09-28 18:20 ` Bernhard Fischer
2007-09-28 19:01 ` Ulf Samuelsson
2007-09-28 19:16 ` Bernhard Fischer
2007-09-28 20:49 ` Clark Rawlins
2007-09-28 20:58 ` Bernhard Fischer [this message]
2007-09-29 16:50 ` Clark Rawlins
2007-09-29 17:10 ` Bernhard Fischer
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=20070928205833.GA20951@aon.at \
--to=rep.dot.nop@gmail.com \
--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