All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Nielsen <a.nielsen@shikadi.net>
To: buildroot@busybox.net
Subject: [Buildroot] binutils doesn't like -elf2flt option
Date: Mon, 17 Jun 2013 17:10:39 +1000	[thread overview]
Message-ID: <kpmcpb$lbo$1@ger.gmane.org> (raw)
In-Reply-To: <51BEAB3A.8010408@mind.be>

Thomas Petazzoni wrote:
> Are we talking about the cross binutils (i.e the one that runs on your
> development PC and generates code for your target platform), or the
> target binutils (i.e the one that runs on your target platform and
> generates code for your target platform) ?

I'm not entirely sure.  I can run "make binutils" to cause the error, so I'm 
assuming it must be target binutils.  But then that doesn't make sense, 
because I have not configured buildroot to compile binutils for my target 
platform (BR2_PACKAGE_BINUTILS=n).

There is a file buildroot/build/host-binutils-2.23.2/.stamp_built so I am 
guessing that means the cross binutils worked.  So I am not sure why it is 
trying to compile target binutils?

Here's my buildroot config if it helps: 
<http://www.shikadi.net/files/buildroot/2013-06-17.br.binutils_elf2flt_err.config>

Be warned there are a couple of new options in there I have added myself.

Arnout Vandecappelle wrote:
>   elf2flt already depends on binutils (it uses libbfd), so this won't work.
> And as Thomas mentioned, this is only relevant for target-binutils (which you
> probably don't even need).

Hmm yes, since I'm not producing BFLT binaries (as they will run on the host) 
I can see that I should not be specifying these options.  However since the 
host/cross binutils builds successfully, it seems that part is working.

>   However, it looks like there is no explicit dependency on elf2flt when
> building the toolchain. Probably elf2flt should be added to BASE_TARGETS, to
> make sure it gets built before all the rest.

Would this mean elf2flt gets built before the target binutils, should I choose 
to enable it?  I am guessing that is what needs to happen for this to work 
correctly, assuming target binutils should be built.

Many thanks,
Adam.

  reply	other threads:[~2013-06-17  7:10 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 [this message]
2013-06-18 16:00     ` Arnout Vandecappelle
2013-06-18 20:34       ` Adam Nielsen
2013-06-19  6:25         ` Thomas Petazzoni
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='kpmcpb$lbo$1@ger.gmane.org' \
    --to=a.nielsen@shikadi.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.