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] minnowboard_max_defconfig: grub2 needs WCHAR
Date: Fri, 11 Aug 2017 15:29:44 +0200	[thread overview]
Message-ID: <20170811152944.62b3f48e@windsurf> (raw)
In-Reply-To: <20170810212805.27808-1-arnout@mind.be>

Hello,

On Thu, 10 Aug 2017 23:28:05 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> Since commit 5ffafd2353f5d67 (grub2: bump up version), grub2 needs a
> toolchain with WCHAR support. However, the defconfigs that use grub2
> were not updated at the time.
> 
> Add BR2_TOOLCHAIN_BUILDROOT_WCHAR=y to minnowboard_max_defconfig.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Erico Nunes <nunes.erico@gmail.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> Cc: Vincent Stehl? <vincent.stehle@intel.com>
> ---
> The following other defconfigs also use grub2.

I've applied to master. However, I'm not entirely happy with the fact
that grub2 requires wchar, but it's maybe a dependency that can be
removed once we introduce grub2-tools
(http://patchwork.ozlabs.org/patch/755651/).

Anyway for now, adding the wchar option in the minnowboard defconfig is
the only option we have.

Best regards,

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

      reply	other threads:[~2017-08-11 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 21:28 [Buildroot] [PATCH] minnowboard_max_defconfig: grub2 needs WCHAR Arnout Vandecappelle
2017-08-11 13:29 ` 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=20170811152944.62b3f48e@windsurf \
    --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