GNU bug report logs - #66753
grep 3.8 now needs pcre2 as input, not pcre

Previous Next

Package: guix;

Reported by: Matt Beshara <m <at> mfa.pw>

Date: Wed, 25 Oct 2023 22:43:01 UTC

Severity: normal

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Matt Beshara <m <at> mfa.pw>
Subject: bug#66753: closed (Re: bug#66753: grep 3.8 now needs pcre2 as
 input, not pcre)
Date: Mon, 22 Jan 2024 04:35:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#66753: grep 3.8 now needs pcre2 as input, not pcre

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 66753 <at> debbugs.gnu.org.

-- 
66753: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66753
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Matt Beshara <m <at> mfa.pw>
Cc: 66753-done <at> debbugs.gnu.org
Subject: Re: bug#66753: grep 3.8 now needs pcre2 as input, not pcre
Date: Sun, 21 Jan 2024 23:34:30 -0500
Hi,

Matt Beshara <m <at> 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

[Message part 3 (message/rfc822, inline)]
From: Matt Beshara <m <at> mfa.pw>
To: bug-guix <at> gnu.org
Subject: grep 3.8 now needs pcre2 as input, not pcre
Date: Thu, 26 Oct 2023 09:21:24 +1100
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

1. https://github.com/pulseaudio-equalizer-ladspa/equalizer



This bug report was last modified 1 year and 217 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.