Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel header installed with external toolchain ?
Date: Wed, 22 Oct 2008 17:10:35 +0200	[thread overview]
Message-ID: <20081022171035.451de23c@surf> (raw)

Hi,

I'm using Buildroot with an external toolchain, but after every cleanup
of the tree, the next 'make' will trigger the download of the kernel
source code and the installation of kernel headers. I'm wondering why
this is necessary, since the external toolchain already have the
headers.

Isn't this a bug of the external toolchain management ?

Thanks,

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

             reply	other threads:[~2008-10-22 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 15:10 Thomas Petazzoni [this message]
2008-10-22 15:37 ` [Buildroot] Kernel header installed with external toolchain ? Peter Korsgaard
2008-10-22 15:48   ` Thomas Petazzoni

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=20081022171035.451de23c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox