From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Antw:Re: libgcc build fails on Fedora15
Date: Fri, 5 Jul 2013 11:21:22 +0200 [thread overview]
Message-ID: <20130705112122.60b12a22@skate> (raw)
In-Reply-To: <1373015044930-47930.post@n4.nabble.com>
Dear Ian Eperson,
On Fri, 5 Jul 2013 02:04:04 -0700 (PDT), Ian Eperson wrote:
> Was there any resolution, or even progress, on the (apparent) legacy
> Fedora:Buildroot incompatibility?
>
> I am getting the same error (libgcc_s.so.1: ELF file OS ABI invalid) across
> a variety of Buildroots from 2009, 2010, 2011 with Fedora Core 16.
>
> Any guidance would be useful. Is moving Fedora forward or back likely to
> overcome this (or moving to some other development platform)? Would moving
> forward or back with Buildroot be a better strategy?
>
> The target is for a mature Atmel ARM9 SOC. The assumption was that
> (roughly) aligning the platform, target and Buildroot versions in time was
> likely to maximize compatibility. Clearly not.
I've started a download of a Fedora Core 16 VirtualBox image to be able
to test this and see if I can reproduce.
Can you share your Buildroot .config, and tell us if the problem also
happens with more recent Buildroot versions?
Thanks,
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-07-05 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 13:25 [Buildroot] libgcc build fails on Fedora15 MARCEL JANSSEN
2011-09-24 15:48 ` Thomas Petazzoni
2011-09-24 17:58 ` [Buildroot] Antw:Re: " MARCEL JANSSEN
2013-07-05 9:04 ` Ian Eperson
2013-07-05 9:21 ` Thomas Petazzoni [this message]
2013-07-08 8:09 ` Ian Eperson
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=20130705112122.60b12a22@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