public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: pcre regexps in git?
Date: Fri, 25 Feb 2022 08:56:25 +0000	[thread overview]
Message-ID: <20220225085625.yfmiauyhxdradfzf@lucy.dinwoodie.org> (raw)
In-Reply-To: <20220224213229.berg5rjisexeuue3@lucy.dinwoodie.org>

On Thu, Feb 24, 2022 at 09:32:29PM +0000, Adam Dinwoodie wrote:
> On Thu, Feb 24, 2022 at 04:19:13PM -0500, Anthony Heading wrote:
> > Hi,
> > I appreciate this is just a birthday wish-list item, but...
> > 
> > % git grep -P hopeful...
> > fatal: cannot use Perl-compatible regexes when not compiled with USE_LIBPCRE
> > 
> > It would be lovely (well, at least for me) if this could work.
> 
> Huh.  I think that used to work, so if it broke, it presumably broke
> somewhere during the Cygwin Git build process wrangling I've been doing
> of late.  I'll see what I can do to get it working again for you!

It looks like this actually broke some time ago, when the upstream Git
project moved from using libpcre1 to libpcre2, which I didn't spot, and
so didn't realise I needed to update the set of dependencies that are
installed for building Git.  Git's build-time config system is set up
such that, if it can't find a library it wants but doesn't strictly
need, it'll just silently carry on without it, so there's no indication
that there's any function missing until someone notices and complains.
So thank you, Anthony, for noticing and complaining!

(The above is not entirely true: fairly recently upstream Git added --
after I pointed out exactly this problem with a different library -- the
ability to tell the Git test suite that it should expect certain
function to be available regardless of what libraries are installed.
But I've not yet got around to setting that up for the Cygwin Git
builds, and it's unlikely to have caught this problem anyway, since it
predates that function being available.)

Anyway, the key fix here should be pretty straightforward; I think it'll
just be a case of rebuilding Git on a build server that has libpcre2
rather than libpcre1 installed.  Currently the Git builds are failing
for entirely unrelated reasons -- I understand the problem but I'm not
yet certain what the right fix is -- but I'm currently expecting to be
able to sort this all out within a week.

  parent reply	other threads:[~2022-02-25  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 21:19 Anthony Heading
2022-02-24 21:32 ` Adam Dinwoodie
2022-02-24 23:54   ` Allen Hewes
2022-02-25  1:45   ` Anthony Heading
2022-02-25  1:54     ` Allen Hewes
2022-02-25  8:56   ` Adam Dinwoodie [this message]
2022-02-25  0:27 ` Yasuhiro Kimura

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=20220225085625.yfmiauyhxdradfzf@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).