From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [noMMU] How to generate FLAT executable for busybox?
Date: Wed, 31 Jul 2013 15:11:14 +0200 [thread overview]
Message-ID: <20130731151114.481b6485@skate> (raw)
In-Reply-To: <CAFRkauBReYkcyUzaOdHk586wNm3vgP0Uaztv3vgvfvz608NidA@mail.gmail.com>
Dear Axel Lin,
On Wed, 31 Jul 2013 21:05:56 +0800, Axel Lin wrote:
> Just try to figure out if any platform can build FLAT executable.
> So I just tested build for blackfin (BR2_bfin).
> ( I don't have any customization for this blackfin build test,
> only run make menuconfig and select blackfin. Test with current git tree. )
>
> I thought I should have a FLAT executable, however it produces ELF executable.
> $ file output/target/bin/busybox
> output/target/bin/busybox: setuid ELF 32-bit LSB executable, Analog
> Devices Blackfin, version 1 (SYSV), statically linked, stripped
Yeah, that's broken.
> BTW, I found BR2_ELF2FLT is invisible for BR2_bfin.
>
> package/elf2flt/Config.in.host:
> config BR2_PACKAGE_HOST_ELF2FLT
> bool "Enable elf2flt support?"
> depends on BR2_arm || BR2_sh || BR2_sparc
>
> Does this mean blackfin does not need elf2flt tool?
No, it means that the internal toolchain handling of FLAT binaries and
elf2flt is broken.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-31 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 5:40 [Buildroot] [noMMU] How to generate FLAT executable for busybox? Axel Lin
2013-07-29 9:27 ` Axel Lin
2013-07-31 13:05 ` Axel Lin
2013-07-31 13:11 ` 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=20130731151114.481b6485@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.