From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] binutils doesn't like -elf2flt option
Date: Wed, 19 Jun 2013 08:25:57 +0200 [thread overview]
Message-ID: <20130619082557.447efce8@skate> (raw)
In-Reply-To: <kpqg93$v74$1@ger.gmane.org>
Dear Adam Nielsen,
On Wed, 19 Jun 2013 06:34:48 +1000, Adam Nielsen wrote:
> Sorry, to clarify - I get the error running just "make", but if I want to
> experiment by changing build flags, I can run "make binutils" to skip
> recompiling gcc, uclibc, etc. and just attempt the bit that recently failed.
I believe you're still confusing the target binutils (which gets built
when you run "make binutils") with the cross binutils (which gets built
together with gcc, uclibc as part of the cross-compilation toolchain,
this one can be rebuilt explicitly by doing "make host-binutils").
> This is just a timesaver when testing though, the real problem is that I still
> get these errors from the target binutils when running "make".
Do you need the target binutils? If you need BFLT support, your target
system has no MMU, so is probably a bit memory limited, so what would
you need to have binutils on your target on a small system?
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-06-19 6:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 10:26 [Buildroot] binutils doesn't like -elf2flt option Adam Nielsen
2013-06-16 16:03 ` Thomas Petazzoni
2013-06-17 6:22 ` Arnout Vandecappelle
2013-06-17 7:10 ` Adam Nielsen
2013-06-18 16:00 ` Arnout Vandecappelle
2013-06-18 20:34 ` Adam Nielsen
2013-06-19 6:25 ` Thomas Petazzoni [this message]
2013-06-19 8:03 ` Adam Nielsen
2013-06-19 8:21 ` Thomas Petazzoni
2013-06-19 9:56 ` Adam Nielsen
2013-06-19 10:06 ` Thomas Petazzoni
2013-06-19 10:11 ` Adam Nielsen
2013-06-19 10:16 ` Thomas Petazzoni
2013-06-20 9:16 ` Adam Nielsen
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=20130619082557.447efce8@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