From: Junio C Hamano <gitster@pobox.com>
To: Richard Lloyd <richard.lloyd@connectinternetsolutions.com>
Cc: git@vger.kernel.org
Subject: Re: Systems with old regex system headers/libraries don't pick up git's compat/regex header file
Date: Thu, 06 Oct 2016 11:25:48 -0700 [thread overview]
Message-ID: <xmqqeg3tl4gj.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <9f43a2f1-5d7e-3a2e-5a83-40e92ab0d7b5@connectinternetsolutions.com> (Richard Lloyd's message of "Thu, 6 Oct 2016 10:15:49 +0100")
Richard Lloyd <richard.lloyd@connectinternetsolutions.com> writes:
> git ships with a compat/regex tree containing a recent regex
> release, presumably with the intention of allowing systems with
> either no regex or an old regex installed to use the newer compat
> version.
Quick question. Does NO_REGEX help? cf. Makefile
# Define NO_REGEX if your C library lacks regex support with REG_STARTEND
# feature.
next prev parent reply other threads:[~2016-10-06 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 9:15 Systems with old regex system headers/libraries don't pick up git's compat/regex header file Richard Lloyd
2016-10-06 18:25 ` Junio C Hamano [this message]
2016-10-06 19:11 ` Jeff King
2016-10-07 15:45 ` Richard Lloyd
2016-10-07 16:06 ` Jeff King
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=xmqqeg3tl4gj.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=richard.lloyd@connectinternetsolutions.com \
/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