From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dependencies: Add host prerequisite for elf2flt
Date: Wed, 4 Sep 2013 13:19:00 +0200 [thread overview]
Message-ID: <20130904131900.7225d262@skate> (raw)
In-Reply-To: <52270CBA.1000603@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 04 Sep 2013 07:34:34 -0300, Gustavo Zacarias wrote:
> On 09/04/2013 05:51 AM, Thomas Petazzoni wrote:
> > I don't think host-elf2flt should be added at this level of dependency.
> > If I understand correctly elf2flt, it interfaces with the linker, so I
> > believe making elf2flt a dependency of binutils would probably make a
> > bit more sense.
>
> It's already done correctly in the dependency deparment...
>
> HOST_ELF2FLT_DEPENDENCIES = host-binutils host-zlib
What I was suggesting is that host-elf2flt should have been a
dependency of host-binutils. But that's obviously wrong, since elf2flt
requires the libbfd library I suspect.
> The problem is it's never pulled in when it's necessary - before the
> real packages start building, so adding it up as a gcc dep when
> BR2_BINFMT_FLAT=y would be appropiate.
Indeed. If it's not needed during the gcc build, one solution is to add
its as a dependency in host-gcc-final.
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-09-04 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 8:16 [Buildroot] [PATCH] dependencies: Add host prerequisite for elf2flt Axel Lin
2013-09-04 8:51 ` Thomas Petazzoni
2013-09-04 10:34 ` Gustavo Zacarias
2013-09-04 11:19 ` Thomas Petazzoni [this message]
2013-09-04 11:27 ` Gustavo Zacarias
2013-09-04 11:34 ` Thomas Petazzoni
[not found] ` <CAAXf6LW+C8GpD8vh4D3xQKNHggYOXmbG8xSRBttuYt8+usCnoA@mail.gmail.com>
2013-09-04 12:14 ` Gustavo Zacarias
2013-09-04 12:16 ` Thomas De Schampheleire
2013-09-04 12:14 ` Thomas De Schampheleire
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=20130904131900.7225d262@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