From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/git: add optional support for pcre2
Date: Thu, 23 Nov 2017 23:22:36 +0100 [thread overview]
Message-ID: <20171123232236.75b99266@windsurf.lan> (raw)
In-Reply-To: <20171031183657.27406-2-bernd.kuhls@t-online.de>
Hello,
On Tue, 31 Oct 2017 19:36:57 +0100, Bernd Kuhls wrote:
> Renamed --with-libpcre to --with-libpcre1. Currently --with-libpcre
> activates pcre1 support but this can change in the future to pcre2:
> https://github.com/git/git/blob/df7fd961a9d9ba60840ffc0868d36cc3db2aec74/configure.ac#L258
>
> Please note that we cannot use --with-/--without because it will lead
> to an error reported by configure, for example
>
> --with-libpcre1 --without-libpcre2
>
> will produce
>
> configure: error: Only supply one of --with-libpcre1 or --with-libpcre2!
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> v2: fixed bug when "--with-libpcre1 --without-libpcre2" is used
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-23 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 18:36 [Buildroot] [PATCH v2 1/2] package/git: bump version to 2.15.0 Bernd Kuhls
2017-10-31 18:36 ` [Buildroot] [PATCH 2/2] package/git: add optional support for pcre2 Bernd Kuhls
2017-11-23 22:22 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-31 8:16 [Buildroot] [PATCH 1/2] package/git: bump version to 2.15.0 Bernd Kuhls
2017-10-31 8:16 ` [Buildroot] [PATCH 2/2] package/git: add optional support for pcre2 Bernd Kuhls
2017-10-31 8:30 ` Bernd Kuhls
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=20171123232236.75b99266@windsurf.lan \
--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