From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why elf2flt is built *after* busybox
Date: Tue, 3 Sep 2013 19:34:17 +0200 [thread overview]
Message-ID: <20130903193417.1a092fd5@skate> (raw)
In-Reply-To: <1378225250.11000.4.camel@phoenix>
Dear Axel Lin,
On Wed, 04 Sep 2013 00:20:50 +0800, Axel Lin wrote:
> Just enable elf2flt and start build.
> From the build log I found the build system build busybox before
> elf2flt. Is this normal?
> I thought elf2flt needs to be ready before building other packages?
Because elf2flt support is broken and someone needs to fix it. You've
already sent several e-mails about this. Gustavo Zacarias is working on
improving the elf2flt, but on a spare time basis, so it's progressing
as time and motivation permits.
Sorry to be a bit rude, but if you want things to move forward faster,
either send patches to fix the problems and get the thing working, or
hire someone to do this work for you. I'm sure ARM noMMU support in
Buildroot will improve, because there are more and more Cortex-M
systems that are capable of running Linux, but it's not something that
is currently well supported in Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-03 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 16:20 [Buildroot] Why elf2flt is built *after* busybox Axel Lin
2013-09-03 17:34 ` Thomas Petazzoni [this message]
2013-09-03 23:57 ` Axel Lin
2013-09-04 2:04 ` Axel Lin
2013-09-04 6:50 ` Thomas De Schampheleire
2013-09-04 7: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=20130903193417.1a092fd5@skate \
--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