From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/01] sngrep: fix wchar detection.
Date: Wed, 31 May 2017 22:07:12 +0200 [thread overview]
Message-ID: <20170531220712.72c0e405@free-electrons.com> (raw)
In-Reply-To: <20170525144749.19333-1-aduskett@codeblue.com>
Hello,
On Thu, 25 May 2017 10:47:49 -0400, Adam Duskett wrote:
> Ncurses detection is currently broken in buildroot.
>
> This patch does the following:
> - Add SNGREP_CHECK_SCRIPT to configure.ac which checks for a
> libname, a function in that library, sets a define if found, and
> if not found, moves on to the next part. This is taken from the
> htop configure.ac.
>
> - Adds SNGREP_CHECK_LIB to configure.ac which checks for a
> library, a function within that library, sets a define if that function
> is found, and if not found, moves on to the next part.
> This is taken from the htop configure.ac
>
> - Modifies scrollbar.h and ui_panel.h to include <wctypes.h> instead of
> <ncursesw/ncurses.h> if unicode is supported.
>
> Signed-off-by: Adam Duskett <aduskett@codeblue.com>
> ---
> .../sngrep/0001-fix-ncurses-wchar-detection.patch | 119 +++++++++++++++++++++
Could you try first to upstream this in the sngrep project? It's a
non-trivial change, so it would be nice to get upstream approval on
this.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-31 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 14:47 [Buildroot] [PATCH 01/01] sngrep: fix wchar detection Adam Duskett
2017-05-31 20:07 ` 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=20170531220712.72c0e405@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