From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Toolchain problems. About toolchains in Buildroot ?
Date: Mon, 27 Oct 2008 16:03:17 +0100 [thread overview]
Message-ID: <20081027160317.16d960a0@surf> (raw)
In-Reply-To: <87bpx6pdw5.fsf@macbook.be.48ers.dk>
Le Mon, 27 Oct 2008 10:48:26 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> What problems do you have with the buildroot toolchains?
Two problems, on ARM (the only architecture I'm using Buildroot for) :
* EABI kernel build failures. The kernel couldn't find some weird eabi
function, which is implemented in libgcc, but the kernel is not
supposed to be linked with libgcc. It's probably due to incorrect
code being generated by the compiler. I can report the exact is
required.
* A DirectFB+Gtk build with a sample Hello World application (not
using Gtk, but linked against Gtk) crashes on start-up
("Segmentation fault"). Seems that the crash is occuring somewhere
in uClibc, but I'm unsure.
Both of these problems go away when I use an external toolchain built
with crosstool-ng.
Generally-speaking, it seems that the toolchain in Buildroot are not
maintained as much as it would be necessary to keep properly working
toolchains. It seems that Bernhard Fischer is doing some work on this
front, but on his Git tree, and the changes don't get integrated back
into Buildroot SVN (fragmentation is a shame, IMO).
And again, my opinion on this is that Buildroot should probably focus
on one thing: building root filesystems. Building toolchains is another
job, usually done separatly from building the root filesystem, so
having two different projects makes sense. The crosstool-ng guys are
doing a pretty good job, keeping their scripts up-to-date with the
latest versions of gcc, binutils, uClibc and others, creating stable
releases, getting quite some user testing and feedback, etc. They also
provide an interesting feature: generate toolchain for glibc, uClibc,
and eglibc. So, I'd say that instead of fragmenting the energies it
would probably be nice if Buildroot focused on building root
filesystems, leaving the work of building the toolchain to
crosstool-ng. But that's just my opinion, of course.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2008-10-27 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 0:16 [Buildroot] [PATCH] libglib2: remove $(DISABLE_NLS) from configure options Markus Heidelberg
2008-10-26 20:02 ` Peter Korsgaard
2008-10-27 7:07 ` Markus Heidelberg
2008-10-27 9:13 ` Peter Korsgaard
2008-10-27 9:30 ` Thomas Petazzoni
2008-10-27 9:48 ` Peter Korsgaard
2008-10-27 15:03 ` Thomas Petazzoni [this message]
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=20081027160317.16d960a0@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