unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Matt Beshara <m@mfa.pw>
Cc: 66753-done@debbugs.gnu.org
Subject: bug#66753: grep 3.8 now needs pcre2 as input, not pcre
Date: Sun, 21 Jan 2024 23:34:30 -0500	[thread overview]
Message-ID: <87fryq56ll.fsf@gmail.com> (raw)
In-Reply-To: <87zg06496e.fsf@mfa.pw> (Matt Beshara's message of "Thu, 26 Oct 2023 09:21:24 +1100")

Hi,

Matt Beshara <m@mfa.pw> writes:

> Hi Guix people,
> I have been working on creating a package definition for
> pulseaudio-equalizer¹ and when built with the current definition of
> the grep package, it prints this error message when running:
>
> grep: Perl matching not supported in a --disable-perl-regexp build
> grep: write error: Broken pipe
>
> Searching for that error message, I came across this:
> https://trac.macports.org/ticket/65800
>
> So it seems that, for version 3.8, the pcre input package for grep
> should be changed to pcre2.  I have made this change in a new
> definition which inherits grep and told my pulseaudio-equalizer
> package to use that as a propagated input, and that causes the error
> to go away.  For the sake of completeness, here’s the definition I
> used:
>
> (define grep-fixed
>  (package
>    (inherit grep)
>    (inputs (list pcre2))))
>
> Best wishes,
> Matt

This appears to have been fixed independently by spacecadet in commit
5b0cea02358044f0cc695bacc3f44db1e220239b ("gnu: grep: Fix PCRE matches
(grep -P).").

Closing!

-- 
Thanks,
Maxim




      reply	other threads:[~2024-01-22  4:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 22:21 bug#66753: grep 3.8 now needs pcre2 as input, not pcre Matt Beshara
2024-01-22  4:34 ` Maxim Cournoyer [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fryq56ll.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=66753-done@debbugs.gnu.org \
    --cc=m@mfa.pw \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).