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] [PATCHv2] libedit: really needs wchar support
Date: Wed, 31 Jul 2013 19:14:59 +0200	[thread overview]
Message-ID: <20130731171459.GC3448@free.fr> (raw)
In-Reply-To: <1375290755-15756-1-git-send-email-gustavo@zacarias.com.ar>

On 2013-07-31 14:12 -0300, Gustavo Zacarias spake thusly:
> 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>

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

> ---
>  package/libedit/Config.in  |  4 ++++
>  package/libedit/libedit.mk | 10 +++-------
>  2 files changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/package/libedit/Config.in b/package/libedit/Config.in
> index 4747a38..72b0cf1 100644
> --- a/package/libedit/Config.in
> +++ b/package/libedit/Config.in
> @@ -1,5 +1,6 @@
>  config BR2_PACKAGE_LIBEDIT
>  	bool "libedit"
> +	depends on BR2_USE_WCHAR
>  	select BR2_PACKAGE_NCURSES
>  	help
>  	  The editline library (from BSD) provides generic line editing
> @@ -12,3 +13,6 @@ config BR2_PACKAGE_LIBEDIT
>  	  in Buildroot as it makes it much simpler than using the upstream
>  	  sources which require pmake:
>  	  http://www.thrysoee.dk/editline/
> +
> +comment "libedit requires a toolchain with WCHAR support"
> +	depends on !BR2_USE_WCHAR
> diff --git a/package/libedit/libedit.mk b/package/libedit/libedit.mk
> index 6769fdc..0ff418a 100644
> --- a/package/libedit/libedit.mk
> +++ b/package/libedit/libedit.mk
> @@ -12,6 +12,9 @@ LIBEDIT_DEPENDENCIES    = ncurses
>  # We're patching configure.ac
>  LIBEDIT_AUTORECONF      = YES
> 
> +# Doesn't really support !wchar, but support is disabled otherwise
> +LIBEDIT_CONF_OPT += --enable-widec
> +
>  # Note: libbsd required for *vis functions, but works only with a toolchain
>  # with __progname; otherwise, some features are disabled, as if libbsd was
>  # missing entirely.
> @@ -19,11 +22,4 @@ ifeq ($(BR2_PACKAGE_LIBBSD),y)
>  LIBEDIT_DEPENDENCIES   += libbsd
>  endif
> 
> -# Wide-char support is not autodetected by configure, we have to help a bit.
> -ifeq ($(BR2_TOOLCHAIN_EXTERNAL_WCHAR),y)
> -LIBEDIT_CONF_OPT       += --enable-widec
> -else
> -LIBEDIT_CONF_OPT       += --disable-widec
> -endif
> -
>  $(eval $(autotools-package))
> --
> 1.8.1.5
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  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:[~2013-07-31 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 17:12 [Buildroot] [PATCHv2] libedit: really needs wchar support Gustavo Zacarias
2013-07-31 17:14 ` Yann E. MORIN [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=20130731171459.GC3448@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