From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot error
Date: Tue, 15 Nov 2016 22:47:08 +0100 [thread overview]
Message-ID: <20161115224708.043f0c31@free-electrons.com> (raw)
In-Reply-To: <8dee00da-0ff9-66de-2baf-c0b1f39dc96e@mind.be>
Hello,
On Tue, 15 Nov 2016 22:39:32 +0100, Arnout Vandecappelle wrote:
> > >>>> linux-headers custom Syncing from source dir /home/mikeb/sandbox/buildroot-2016.08/uClinux-dist
> > rsync -au --chmod=u=rwX,go=rX --exclude .svn --exclude .git --exclude .hg --exclude .bzr --exclude CVS /home/mikeb/sandbox/buildroot-2016.08/uClinux-dist/ /home/mikeb/sandbox/buildroot-2016.08/output/build/linux-headers-custom
>
> Either the linux tree in uClinux-dist is so old that it doesn't have the
> "headers_install" target yet (I think that's from 2.6.10-ish), or the tree
> you're pointing to is not actually a linux tree. In the first case, you also
> misconfigured your kernel headers, because you claim it's 4.7. But you probably
> just took the first thing you saw :-)
uClinux-dist is the name of the "distribution" around uClinux, and
uClinux-dist is pretty much a build system, like Buildroot. So it seems
like Michael has used the source code of a build system, and offered it
to Buildroot as the source of the Linux kernel. Obviously, this isn't
going to work very well.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-15 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 21:11 [Buildroot] Buildroot error Michael Brainerd
2016-11-15 21:39 ` Arnout Vandecappelle
2016-11-15 21:47 ` Thomas Petazzoni [this message]
2016-11-17 17:38 ` Michael Brainerd
2016-11-17 22:31 ` 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=20161115224708.043f0c31@free-electrons.com \
--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