Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/3] busybox: disable nslookup applet
Date: Tue, 14 Jul 2015 18:31:26 +0200	[thread overview]
Message-ID: <20150714183126.3a0ed496@free-electrons.com> (raw)
In-Reply-To: <1436890174-23236-1-git-send-email-guido@vanguardiasur.com.ar>

Dear Guido Mart?nez,

On Tue, 14 Jul 2015 13:09:32 -0300, Guido Mart?nez wrote:
> Some toolchains have no resolver support (res_* family), so they fail to
> build this applet (which is the only user of those functions). Instead
> of selectively disabling it on such limited toolchains, just drop it
> from the default config, since (to the best of my knowledge) is not
> widely used.
> 
> Signed-off-by: Guido Mart?nez <guido@vanguardiasur.com.ar>

I know this solution was suggested to you instead of adding a new
toolchain option that tells us whether resolver support is available or
not.

However, the problem with the solution of changing the Busybox config
file is that it fixes Busybox only: there will possibly be plenty of
other packages using res_*(). And we will have no way to fix those
packages in a proper way, except possibly by making them 'depends
on !BR2_TOOLCHAIN_EXTERNAL_OSELAS_ARM_CORTEX_M3_201412'. But if other
OSELAS toolchains for other architectures also lack resolver support,
then we will have to add more and more of those exclusions.

Conclusion: I am wondering if your initial solution was not the right
one.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-07-14 16:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 17:33 [Buildroot] [PATCH v3 0/4] Add ARM Cortex-M3 support Guido Martínez
2015-06-26 17:33 ` [Buildroot] [PATCH 1/4] arm: update processor types Guido Martínez
2015-06-27 10:24   ` Yann E. MORIN
2015-06-26 17:33 ` [Buildroot] [PATCH 2/4] toolchain: allow for stupid toolchains Guido Martínez
2015-06-27 10:28   ` Yann E. MORIN
2015-06-26 17:33 ` [Buildroot] [PATCH 3/4] toolchain: introduce BR2_TOOLCHAIN_HAS_RESOLVER Guido Martínez
2015-06-27 10:39   ` Yann E. MORIN
2015-06-26 17:33 ` [Buildroot] [PATCH 4/4] toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain Guido Martínez
2015-06-27 12:42   ` Yann E. MORIN
2015-06-28 12:34 ` [Buildroot] [PATCH v3 0/4] Add ARM Cortex-M3 support Thomas Petazzoni
2015-06-29 15:01   ` Guido Martínez
2015-07-14 15:11 ` [Buildroot] [PATCH v4 0/3] " Guido Martínez
2015-07-14 15:11   ` [Buildroot] [PATCH v4 1/3] busybox: disable nslookup applet Guido Martínez
2015-07-14 15:11   ` [Buildroot] [PATCH v4 2/3] toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain Guido Martínez
2015-07-14 15:42     ` Baruch Siach
2015-07-14 15:57       ` Guido Martínez
2015-07-14 15:11   ` [Buildroot] [PATCH v4 3/3] toolchain: disable internal for blackfin Guido Martínez
2015-07-14 15:43     ` Baruch Siach
2015-07-14 15:58       ` Guido Martínez
2015-07-14 19:20     ` Waldemar Brodkorb
2015-07-14 16:09   ` [Buildroot] [PATCH v5 1/3] busybox: disable nslookup applet Guido Martínez
2015-07-14 16:09     ` [Buildroot] [PATCH v5 2/3] toolchain-external: add OSELAS 2014.12.0 Cortex-M3 toolchain Guido Martínez
2015-07-14 16:09     ` [Buildroot] [PATCH v5 3/3] toolchain: disable internal for Cortex-M3 Guido Martínez
2015-07-14 16:31     ` Thomas Petazzoni [this message]
2015-07-14 16:55       ` [Buildroot] [PATCH v5 1/3] busybox: disable nslookup applet Thomas Petazzoni
2015-07-14 17:10         ` Gustavo Zacarias
2015-07-15 17:19         ` Guido Martínez

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=20150714183126.3a0ed496@free-electrons.com \
    --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