From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: toolchaintoolchain/external-toolchain
Date: Tue, 04 Nov 2008 20:22:44 +0100 [thread overview]
Message-ID: <873ai71ekb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20081104182314.580215e5@surf> (Thomas Petazzoni's message of "Tue\, 4 Nov 2008 18\:23\:14 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
Thomas> The second option ? same version as linux headers ? clearly
Thomas> cannot work with my patches: since we're using an external
Thomas> toolchain, there's no version of linux headers defined in
Thomas> Buildroot.
Thomas> So my proposal is:
Thomas> 1) remove the option "linux (same version as linux headers)"
Thomas> when an external toolchain is used ;
Seems logical.
Thomas> Grant Likely recently sent a patch adding the ability to get the kernel
Thomas> for a Git repository. See
Thomas> http://buildroot.uclibc.org/lists/buildroot/2008-October/011037.html.
Thomas> This patch hasn't been integrated to Buildroot, yet.
Yeah, it's still on my todo list.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-11-04 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 10:18 [Buildroot] svn commit: trunk/buildroot: toolchain toolchain/external-toolchain jacmet at uclibc.org
2008-11-03 21:09 ` [Buildroot] svn commit: trunk/buildroot: toolchaintoolchain/external-toolchain hartleys
2008-11-03 23:17 ` Thomas Petazzoni
[not found] ` <BD79186B4FD85F4B8E60E381CAEE1909C9177C@mi8nycmail19.Mi8.com>
2008-11-04 17:23 ` Thomas Petazzoni
2008-11-04 19:10 ` [Buildroot] [PATCH] Kernel build fix related to external toolchain use Thomas Petazzoni
2008-11-04 19:59 ` Peter Korsgaard
2008-11-04 19:22 ` Peter Korsgaard [this message]
2008-11-04 19:50 ` [Buildroot] svn commit: trunk/buildroot: toolchaintoolchain/external-toolchain hartleys
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=873ai71ekb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.