From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Antw: Antw:Re: libgcc build fails on Fedora15
Date: Mon, 26 Sep 2011 08:46:24 +0200 [thread overview]
Message-ID: <20110926084624.0851437a@skate> (raw)
In-Reply-To: <7340d14feedea.4e7eccc3@home.nl>
Le Sun, 25 Sep 2011 06:40:03 +0200,
"MARCEL JANSSEN" <korgull@home.nl> a ?crit :
> The log doesn't show the error, but it's printed in the terminal :
> /bin/sh: error while loading shared
> libraries: /admesy/arm/buildroot/output/toolchain/gcc-4.4.6-intermediate/./gcc/libgcc_s.so.1:
> ELF file OS ABI invalid
You're building for the OABI ARM ABI, which almost nobody uses, and
indeed breaks in the configuration you gave. Unless you have strong
reasons to keep working with OABI (legacy binaries that you can't
recompile), I would strongly suggest to use EABI. This is what
everybody uses these days.
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:[~2011-09-26 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 4:40 [Buildroot] Antw: Antw:Re: libgcc build fails on Fedora15 MARCEL JANSSEN
2011-09-26 6:46 ` 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=20110926084624.0851437a@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