Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 09:10:57 -0300	[thread overview]
Message-ID: <20140407121057.GD544@arch.cereza> (raw)
In-Reply-To: <20140407134643.591875e7@skate>

On Apr 07, Thomas Petazzoni wrote:
> Dear Ezequiel Garcia,
> 
> On Mon, 7 Apr 2014 08:43:37 -0300, Ezequiel Garcia wrote:
> 
> > 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.
> 
> We can certainly do some magic in toolchain-external.mk for specific
> toolchains. I just hope the magic is not too horrible :-)
> 

I'm on it.

On the other side, I should really stop fooling around and prepare a mail
asking about these toolchain issues to the Sourcery guys. I'm sorry for being
so lazy with this!

And while we are here... upstream binutils and GCC supports Nios-II,
unfortunately, glibc and uclibc doesn't (well, uclibc supports threadless,
non shared libraries and non-MMU).

The problem with this, is that Altera is forced to move from a custom
syscall ABI to the generic syscall ABI, before upstreaming the kernel and libc
ports. So, I wouldn't count on this being upstreamed anytime soon.
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2014-04-07 12:10 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
2014-04-07 11:46         ` Thomas Petazzoni
2014-04-07 12:10           ` Ezequiel Garcia [this message]
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=20140407121057.GD544@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