From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-05
Date: Mon, 7 Apr 2014 08:43:37 -0300 [thread overview]
Message-ID: <20140407114337.GB544@arch.cereza> (raw)
In-Reply-To: <20140407132720.699be504@skate>
On Apr 07, Thomas Petazzoni wrote:
> Dear Ezequiel Garcia,
>
> On Mon, 7 Apr 2014 08:18:24 -0300, Ezequiel Garcia wrote:
> > On Apr 06, Thomas Petazzoni wrote:
> > > > nios2 | dhcpcd-6.1.0 | NOK | http://autobuild.buildroot.net/results/c32ad4bac5f651502e551f7733f702afaa0e742a/
> > >
> > > Ezequiel, can you look into this?
> > >
> >
> > Ah, yes. Known issue. The kernel headers exported to userspace by the Sourcery
> > toolchain are completely broken. Seems like they used "cp" instead of
> > "make headers_install".
>
> Ok.
>
> > If we want to fix headers in an external toolchain, this issue and others like
> > it will get fixed.
>
> I'm not sure to understand what you mean here, however.
>
OK, let me try to explain this better. If we have a (not too dirty) way of
running some script over the linux headers after an external toolchain has
been installed, we can "sanitize" them.
In other words, we'd be doing the "make headers_install" sed magic ourselves,
given the Sourcery people forgot about it.
Maybe adding something to toolchain-external.mk would work?
Let me do some tests to see if this works.
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-07 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-05 Thomas Petazzoni
2014-04-06 9:08 ` Thomas Petazzoni
2014-04-06 9:48 ` Romain Naour
2014-04-06 12:42 ` Samuel Martin
2014-04-07 11:18 ` Ezequiel Garcia
2014-04-07 11:27 ` Thomas Petazzoni
2014-04-07 11:43 ` Ezequiel Garcia [this message]
2014-04-07 11:46 ` Thomas Petazzoni
2014-04-07 12:10 ` Ezequiel Garcia
2014-04-07 11:27 ` Gustavo Zacarias
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=20140407114337.GB544@arch.cereza \
--to=ezequiel.garcia@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