From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libedit: really needs wchar support
Date: Wed, 31 Jul 2013 19:08:42 +0200 [thread overview]
Message-ID: <20130731190842.51b83cc0@skate> (raw)
In-Reply-To: <1375289757-23151-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 31 Jul 2013 13:55:57 -0300, Gustavo Zacarias wrote:
> wctype.h is always included, even in configure tests.
> Fixes:
> http://autobuild.buildroot.net/results/ed8/ed85b9d688ad8389895e3ecd7a6a18151efc328d/
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/libedit/Config.in | 4 ++++
> package/libedit/libedit.mk | 7 -------
> 2 files changed, 4 insertions(+), 7 deletions(-)
As suggested by Yann on IRC, I'll wait for a version that adds a
--enable-widec to LIBEDIT_CONF_OPT.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-31 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 16:55 [Buildroot] [PATCH] libedit: really needs wchar support Gustavo Zacarias
2013-07-31 17:08 ` 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=20130731190842.51b83cc0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox