Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] toolchain: introduce BR2_TOOLCHAIN_HAS_RESOLVER
Date: Sat, 27 Jun 2015 12:39:32 +0200	[thread overview]
Message-ID: <20150627103932.GD3565@free.fr> (raw)
In-Reply-To: <1435340002-20396-4-git-send-email-guido@vanguardiasur.com.ar>

Guido, All,

On 2015-06-26 14:33 -0300, Guido Mart?nez spake thusly:
> Add a Kconfig option specifying if the toolchain supports name resolving
> (or at least has stubs for it) so we can disable packages that depend on
> that (or they would fail to link). For now, only disable the 'nslookup'
> tool from BusyBox if there's no resolver support.
> 
> For now, every toolchain supports name resolving.

I'm a bit skeptical about this change.

Let's see:
  - adds a new 'select' for all existing external pre-configured
    toolchains;

  - misses the cases for internal toolchain and exterdnal custom
    toolchains;

  - disables nslookup in busybox when resolver is mising;

  - misses the fixing the bind package which can install nslookup, too.

So, I find this is a bit of noise for a relatively infrequent setup. And
you're missing quite a few cases.

I'd rather we disable nslookup from our default busybox configuration.

(Note: the bind case is not a problem for you, because it already
depends on MMU which Cortex-M3 do not have, so bind is inherently
protected from such limited toolchains.)

> Signed-off-by: Guido Mart?nez <guido@vanguardiasur.com.ar>
> ---
>  package/busybox/busybox.mk             |  3 +++
>  toolchain/Config.in                    |  3 +++
>  toolchain/toolchain-external/Config.in | 29 +++++++++++++++++++++++++++++
>  3 files changed, 35 insertions(+)
> 
> diff --git a/package/busybox/busybox.mk b/package/busybox/busybox.mk
> index 090e174..f4e086e 100644
> --- a/package/busybox/busybox.mk
> +++ b/package/busybox/busybox.mk
> @@ -156,6 +156,9 @@ endif
>  # full-blown versions of apps installed by other packages with sym/hard links.
>  define BUSYBOX_NOCLOBBER_INSTALL
>  	$(SED) 's/^noclobber="0"$$/noclobber="1"/' $(@D)/applets/install.sh
> +	$(if $(BR2_TOOLCHAIN_HAS_RESOLVER),,
> +		$(call KCONFIG_DISABLE_OPT,CONFIG_NSLOOKUP,$(@D)/.config)
> +	)

This hunk should go into its own macro, and used in
BUSYBOX_KCONFIG_FIXUP_CMDS, below, like so:

    ifeq ($(BR2_TOOLCHAIN_HAS_RESOLVER),)
    define BUSYBOX_UNSET_NSLOOKUP
        $(call KCONFIG_DISABLE_OPT,CONFIG_NSLOOKUP,$(@D)/.config)
    endef
    endif

    define BUSYBOX_KCONFIG_FIXUP_CMDS
        [existing calls]
        $(BUSYBOX_UNSET_NSLOOKUP)
    endef

But I'd really prefer we just ditch nslookup from our default busybox
configuration, to avoid all this noise.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-06-27 10:39 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 [this message]
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     ` [Buildroot] [PATCH v5 1/3] busybox: disable nslookup applet Thomas Petazzoni
2015-07-14 16:55       ` 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=20150627103932.GD3565@free.fr \
    --to=yann.morin.1998@free.fr \
    --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