From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] nano: work around broken syntax highlighting regexes
Date: Sat, 11 Jul 2015 09:25:43 +0200 [thread overview]
Message-ID: <20150711092543.650825fb@free-electrons.com> (raw)
In-Reply-To: <1432838510-1848-1-git-send-email-pmjdebruijn@pcode.nl>
Dear Pascal de Bruijn,
On Thu, 28 May 2015 20:41:46 +0200, Pascal de Bruijn wrote:
> Signed-off-by: Pascal de Bruijn <pmjdebruijn@pcode.nl>
> ---
> package/nano/nano.mk | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/package/nano/nano.mk b/package/nano/nano.mk
> index 4d47fdb..c6eb29c 100644
> --- a/package/nano/nano.mk
> +++ b/package/nano/nano.mk
> @@ -11,6 +11,9 @@ NANO_LICENSE_FILES = COPYING
> NANO_CONF_OPTS = --without-slang
> NANO_DEPENDENCIES = ncurses
>
> +# work around broken syntax highlighting regexes
> +NANO_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -DGNU_WORDBOUNDS=1"
> +
There was a ./configure option --with-wordbounds to also do this, so I
use that instead of fiddling with CFLAGS.
Committed with that change, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-11 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 18:41 [Buildroot] [PATCH 1/5] nano: work around broken syntax highlighting regexes Pascal de Bruijn
2015-05-28 18:41 ` [Buildroot] [PATCH 2/5] defconfig: update raspberry pi 2 to linux 3.18.14 Pascal de Bruijn
2015-06-28 18:17 ` Yann E. MORIN
2015-05-28 18:41 ` [Buildroot] [PATCH 3/5] defconfig: update raspberry pi dt " Pascal de Bruijn
2015-05-28 18:41 ` [Buildroot] [PATCH 4/5] rpi-firmware: update to match " Pascal de Bruijn
2015-05-28 18:41 ` [Buildroot] [PATCH 5/5] rpi-userland: " Pascal de Bruijn
2015-07-11 7:25 ` 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=20150711092543.650825fb@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