From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Arm build: asm error in libffi?
Date: Thu, 4 Aug 2011 21:49:23 +0200 [thread overview]
Message-ID: <20110804214923.37cc66df@skate> (raw)
In-Reply-To: <CAFzH18j2mFTzSOrf1S9ChgaJ3cGyoxTOOTtCOuX8prUt5rXLzQ@mail.gmail.com>
Le Thu, 4 Aug 2011 12:40:53 +0300,
Dimitri Kaparis <kaparis.dimitri@gmail.com> a ?crit :
> I'm doing a build for arm using a crosstool-ng generated toolchain
> (gcc 4.4.6, uclibc 0.9.30.3).
> With buildroot-2011.05 I'm getting this:
I guess it's a problem with the toolchain, because here libffi builds
just fine with an ARM CodeSourcery toolchain.
Which binutils version does your toolchain has ?
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:[~2011-08-04 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 9:40 [Buildroot] Arm build: asm error in libffi? Dimitri Kaparis
2011-08-04 19:49 ` Thomas Petazzoni [this message]
2011-08-05 7:56 ` Dimitri Kaparis
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=20110804214923.37cc66df@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