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 3/3] efibootmgr: depends on wchar
Date: Wed, 7 Dec 2016 23:48:34 +0100	[thread overview]
Message-ID: <20161207234834.40f51647@free-electrons.com> (raw)
In-Reply-To: <1480979238-18273-4-git-send-email-nunes.erico@gmail.com>

Hello,

On Tue,  6 Dec 2016 00:07:18 +0100, Erico Nunes wrote:

> This "select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT" is slightly
> complicated to handle for the propagated wchar dependency, if the
> unavailability Kconfig "comment" is added.
> Looks like we don't need to always have the wchar dependency as the
> dependency on gettext is optional, however this complicates the mention
> to 'needs wchar' in the Kconfig comment.
> Some packages seem to try to handle this in some smarter way
> (BR2_PACKAGE_LINUX_TOOLS_CPUPOWER) but then the comment is not always
> accurate.
> Please let me know if there is a better way to do this, right now it
> seems to be simpler to just require wchar always.

If you really want to be pedantic, you could write:

	depends on !BR2_NEEDS_GETTEXT || BR2_USE_WCHAR

but it anyway makes the Config.in comment handling a bit annoying. And
it's in fact a bit useless:

 - On glibc, BR2_USE_WCHAR is always 'y', and BR2_NEEDS_GETTEXT is false

 - On musl, BR2_USE_WCHAR is always 'y', and BR2_NEEDS_GETTEXT is false

 - On uClibc, BR2_NEEDS_GETTEXT is 'y', and indeed BR2_USE_WCHAR needs
   to be set.

So in fact, a "depends on BR2_USE_WCHAR" is good enough.

Thanks!

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

  reply	other threads:[~2016-12-07 22:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 23:07 [Buildroot] [PATCH 1/3] efivar: fix comment after uClibc compatibility patch Erico Nunes
2016-12-05 23:07 ` [Buildroot] [PATCH 1/1] gcc: fix powerpc64le arch config name Erico Nunes
2016-12-06 21:58   ` Peter Korsgaard
2016-12-05 23:07 ` [Buildroot] [PATCH 2/3] efivar: introduce BR2_PACKAGE_EFIVAR_ARCH_SUPPORTS Erico Nunes
2016-12-05 23:07 ` [Buildroot] [PATCH 3/3] efibootmgr: depends on wchar Erico Nunes
2016-12-07 22:48   ` Thomas Petazzoni [this message]
2016-12-07 22:47 ` [Buildroot] [PATCH 1/3] efivar: fix comment after uClibc compatibility patch Thomas Petazzoni

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=20161207234834.40f51647@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