From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Problems building for ucLinux/ARM with elf2flt enabled
Date: Thu, 25 Jul 2013 10:11:59 -0300 [thread overview]
Message-ID: <51F1241F.6050609@zacarias.com.ar> (raw)
In-Reply-To: <CBB26B88EF85F6489575628B28ECBE6D43286066BE@ablexc01.internal.novero.com>
On 07/25/2013 07:13 AM, Anna Fischer (novero/Bochum) wrote:
>>> Any pointers would be really appreciated.
>>
>> I'm afraid I'm not the person to help you here, I don't have any
>> experience with flat binaries in buildroot.
>> Others may be better suited. Thomas Petazzoni maybe?
>>
>
> It seems as if by default FLAT binaries are not supported for the ARM architecture. It is only supported for Blackfin devices and m68k. Choosing the target binary format is disabled in by configuration because I use an ARM device.
The ARM nommu internal toolchain needs some work, similar to the
patchset i've sent for blackfin fixes.
For starters the tuple is wrong, it should be *-uclinux-* (instead of
*-linux-*) in package/Makefile.in
And there are other details regarding uclibc configuration for example
to fix.
It would probably be a good idea to add M-series and R-series cortex cpu
definitions too since those are the most likely to be used for nommu.
I'm looking into it but i make no promises, i lack hardware to test this
and qemu doesn't emulate anything useful regarding it.
Regards.
prev parent reply other threads:[~2013-07-25 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 10:02 [Buildroot] Problems building for ucLinux/ARM with elf2flt enabled Anna Fischer
2013-07-24 10:40 ` Thomas De Schampheleire
2013-07-24 11:39 ` Anna Fischer
2013-07-24 11:50 ` Thomas De Schampheleire
2013-07-24 12:05 ` Anna Fischer
2013-07-25 9:45 ` Anna Fischer
2013-07-25 10:03 ` Thomas De Schampheleire
2013-07-25 10:13 ` Anna Fischer
2013-07-25 13:11 ` Gustavo Zacarias [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=51F1241F.6050609@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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