From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>
Subject: Re: grep rebuild?
Date: Fri, 17 Mar 2023 10:15:09 +0100 [thread overview]
Message-ID: <ZBQvnf9BMcualu6A@calimero.vinschen.de> (raw)
In-Reply-To: <ZBQs4CRJ+E7crJkG@calimero.vinschen.de>
On Mar 17 10:03, Corinna Vinschen via Cygwin-apps wrote:
> On Mar 16 18:50, Brian Inglis via Cygwin-apps wrote:
> > On 2023-03-16 10:50, Brian Inglis via Cygwin-apps wrote:
> > > On 2023-03-16 06:08, Corinna Vinschen via Cygwin-apps wrote:
> > > > Hi Brian,
> > > >
> > > > there's a problem with the grep package. It uses the internally
> > > > provided GNULIB regex library.
> > > >
> > > > Unfortunately, that's the default if the system doesn't provide a more
> > > > recent GLibc. Which we'll never do. The problem is this: Native
> > > > language support in GNULIB's regex is *only* available, if it's built as
> > > > part of GLibc.
> > > >
> > > > I'd like to ask you to rebuild grep 3.9 with the
> > > > --without-included-regex option.
> > > >
> > > > That will allow grep to use Cygwin's own regex, which already comes with
> > > > basic native language support, and which I'm working on to sbetter
> > > > support equivalence class and collation symbol expressions.
> > >
> > > Hi Corinna,
> > >
> > > We discussed this and I was going to release grep 3.8 test release 3,
> > > for testing with snapshots or when Cygwin 3.5.0 is released, then grep
> > > 3.9 came out, and I realized grep is updated every few months, so that
> > > went on the back burner. I can do a test release for 3.9-2 with that
> > > configuration change.
> > >
> > > The current release passes all the class tests and works for me and Andrey.
> > > Are there any other implications of language support affecting grep?
> >
> > Config option --without-included-regex no longer seems to build with grep
> > 3.9 on Cygwin - may require glibc regex - or may now autoconfig depending on
> > [g]libc?
> >
> > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
> > dfasearch.o: in function `regex_compile':
> > /usr/src/debug/grep-3.9-2/src/dfasearch.c:159: undefined reference to
> > `re_set_syntax'
>
> What a piece of crap! So you either run a GLibc system, or you're
> forced to use GNULIB regex because grep uses non-standard functions
> in the generic code.
>
> We should switch to FreeBSD grep, it still uses POSIX functions.
> What a laugh...
And just for kicks, FreeBSD grep is mostly option compatible with
GNU grep. The missing options are:
-P, --perl-regexp
--no-ignore-case (but --ignore-case exists)
-y (obsolete anyway)
-T, --initial-tab
-Z (but --null exists)
--group-separator
--no-group-separator
--exclude-from
-I (but --binary-files exists)
-R, --dereference-recursive
I wonder if I should create a freebsd-grep package, installing
its grep as 'bsdgrep' or something....
Corinna
prev parent reply other threads:[~2023-03-17 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 12:08 Corinna Vinschen
2023-03-16 16:50 ` Brian Inglis
2023-03-16 19:31 ` Corinna Vinschen
2023-03-16 19:35 ` Corinna Vinschen
2023-03-17 0:50 ` Brian Inglis
2023-03-17 9:03 ` Corinna Vinschen
2023-03-17 9:15 ` Corinna Vinschen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZBQvnf9BMcualu6A@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=Brian.Inglis@shaw.ca \
--cc=cygwin-apps@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).