From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel header installed with external toolchain ?
Date: Wed, 22 Oct 2008 17:37:43 +0200 [thread overview]
Message-ID: <87r668k5dk.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20081022171035.451de23c@surf> (Thomas Petazzoni's message of "Wed\, 22 Oct 2008 17\:10\:35 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Hi,
Thomas> I'm using Buildroot with an external toolchain, but after every cleanup
Thomas> of the tree, the next 'make' will trigger the download of the kernel
Thomas> source code and the installation of kernel headers. I'm wondering why
Thomas> this is necessary, since the external toolchain already have the
Thomas> headers.
It shouldn't redownload unless you remove your dl dir.
Thomas> Isn't this a bug of the external toolchain management ?
Sounds like it. Sorry, I'm not using the external toolchain stuff, but
patches are welcome.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-10-22 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 15:10 [Buildroot] Kernel header installed with external toolchain ? Thomas Petazzoni
2008-10-22 15:37 ` Peter Korsgaard [this message]
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=87r668k5dk.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.