All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc-initial: Add host-elf2flt dependency when BR2_PACKAGE_HOST_ELF2FLT=y
Date: Thu, 12 Sep 2013 09:23:00 +0200	[thread overview]
Message-ID: <20130912092300.0b3fbb9d@skate> (raw)
In-Reply-To: <CAFRkauDMtOvQj0dx0Xxz2KhWxeHBFERvvU6cohSmpwv5ydRtiQ@mail.gmail.com>

Dear Axel Lin,

On Thu, 12 Sep 2013 09:13:21 +0800, Axel Lin wrote:

> Probably not directly related to this topic, but I have a question
> about the dependency between BR2_BINFMT_FLAT &
> BR2_PACKAGE_HOST_ELF2FLT.
> 
> Why not just make BR2_PACKAGE_HOST_ELF2FLT depend on BR2_BINFMT_FLAT
> rather than "depends on BR2_arm || BR2_bfin || BR2_sh || BR2_sparc"?

As Gustavo pointed out (maybe on IRC ?), BR2_PACKAGE_HOST_ELF2FLT
should simply be removed. There is no need to have a Kconfig option to
host tools when they can simply be built as a dependency of something
else (which is the case here).

The only case for which we add a Kconfig option for host tools is when
this host tool is not built as a dependency of something else, and that
the user may still be interested in building it.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-09-12  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 15:18 [Buildroot] [PATCH] gcc-initial: Add host-elf2flt dependency when BR2_PACKAGE_HOST_ELF2FLT=y Axel Lin
2013-09-04 16:19 ` Thomas Petazzoni
2013-09-11 12:14   ` Gustavo Zacarias
2013-09-12  1:13     ` Axel Lin
2013-09-12  7:23       ` 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=20130912092300.0b3fbb9d@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 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.