From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't get linked into kernel
Date: Sat, 4 May 2013 10:25:52 +0200 [thread overview]
Message-ID: <20130504102552.03b360ae@skate> (raw)
In-Reply-To: <km1kpr$t5l$1@ger.gmane.org>
Dear Adam Nielsen,
On Sat, 04 May 2013 10:29:51 +1000, Adam Nielsen wrote:
> I think I've discovered the problem here. buildroot produces ELF binaries,
> but I cannot compile a kernel with ELF support because BINFMT_ELF depends on
> MMU and my platform is arm7tdmi which does not have an MMU.
>
> This means I need to tell buildroot to produce FLAT executables instead of ELF
> ones. I have enabled elf2flt support in the buildroot config, but it still
> produces ELF binaries.
>
> Is there an option I am missing to make buildroot generate FLAT executables
> instead?
I think the elf2flt stuff hasn't been used in a while, so it isn't very
surprising that it is broken. Your patches are definitely welcome to
fix it, and once it's fixed, I'll add a new toolchain configuration in
our autobuilders to test this configuration on a regular basis.
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-05-04 8:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:37 [Buildroot] initramfs doesn't get linked into kernel Adam Nielsen
2013-04-27 1:17 ` Thomas Petazzoni
2013-04-27 9:53 ` Adam Nielsen
2013-04-27 17:34 ` Thomas Petazzoni
2013-04-27 22:50 ` Adam Nielsen
2013-05-04 0:29 ` Adam Nielsen
2013-05-04 8:25 ` Thomas Petazzoni [this message]
2013-05-04 11:35 ` Adam Nielsen
2013-05-04 17:36 ` Thomas Petazzoni
2013-05-05 1:47 ` Adam Nielsen
2013-05-05 2:11 ` Adam Nielsen
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=20130504102552.03b360ae@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