All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: toolchaintoolchain/external-toolchain
Date: Tue, 4 Nov 2008 18:23:14 +0100	[thread overview]
Message-ID: <20081104182314.580215e5@surf> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909C9177C@mi8nycmail19.Mi8.com>

Hi hartleys,

Please keep the list in Cc, other Buildroot developers can give very
valuable insights, very often better than mine.

Le Mon, 3 Nov 2008 19:09:02 -0500,
"hartleys" <hartleys@visionengravers.com> a ?crit :

> > Oops. Could you give me your Buildroot .config file ? And the error
> message you're having ?
> 
> Attached is the .config

Is this a .config generated with the bare trunk, or with the trunk
modified to remove the two chunks that you mentionned previously ?

Since BR2_KERNEL_HEADERS_2_6_27 is set, I'm inclined to think that this
is a .config after removal of the two chunks.

> > To build the kernel, there are two solutions:
> >  * linux (advanced configuration)
> >  * linux (same version as linux headers)
> >
> > The second solution is probably broken by my change, but the first
> > one seems to work fine here.
> 
> The second is broken with your change.
> 
> I tried the first but it's a bit of a pain. Every time there is a new
> kernel I have to go in an update the values. I guess it's more of a
> nit...

The second option ? same version as linux headers ? clearly cannot work
with my patches: since we're using an external toolchain, there's no
version of linux headers defined in Buildroot.

So my proposal is:

 1) remove the option "linux (same version as linux headers)" when an
    external toolchain is used ;

 2) improve the "advanced" support to suit your needs. What do you mean
    by ? I have to go in and update the values ? ?

What do you think about this ?

> At this point I'm still in development and a lot of the stuff I am
> working on is kernel related. I keep sending off patches that are
> slowly showing up in the newer kernels so I always want the latest
> stuff. I really wish I could figure out how to use git inside
> buildroot...

Grant Likely recently sent a patch adding the ability to get the kernel
for a Git repository. See
http://buildroot.uclibc.org/lists/buildroot/2008-October/011037.html.
This patch hasn't been integrated to Buildroot, yet.

> > I don't use Buildroot to build my kernels, so I missed that problem,
> sorry.
> 
> Not a problem. How else can you cross compile the kernel?

See slides 136 and following in
http://free-electrons.com/doc/embedded_linux_kernel_and_drivers.pdf.

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2008-11-04 17:23 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 [this message]
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         ` [Buildroot] svn commit: trunk/buildroot: toolchaintoolchain/external-toolchain Peter Korsgaard
2008-11-04 19:50         ` 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=20081104182314.580215e5@surf \
    --to=thomas.petazzoni@free-electrons.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 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.