From: "t.rus76 at ya dot ru" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19376] regex reports "Invalid collation character" for Syriac characters
Date: Fri, 18 Dec 2015 15:06:00 -0000 [thread overview]
Message-ID: <bug-19376-716-nJSRiJ4cyb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19376-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19376
--- Comment #2 from t.rus76 at ya dot ru ---
My locale is ru_RU.UTF-8
Yes, I have got the same idea at the beginning.
with LC_CTYPE=en_GB there was no error
but with LC_ALL=en_US.UTF-8 the bug appeared.
Next step I found there are two files regcomp.c in both Glibc and Grep.
I have compared them with Diff. They are very similar, but not exactly.
The one from Grep is obviously newer. But for some reason grep links with glibc
by deafult.
./configure --with-included-regex enforces linking with newer buildin version.
Then it works flawlessly with the same locale.
I am not a native English speaker and hope my explanation are clear enough.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-12-18 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19376-716@http.sourceware.org/bugzilla/>
2015-12-18 12:49 ` bonzini at gnu dot org
2015-12-18 15:06 ` t.rus76 at ya dot ru [this message]
2015-12-18 21:32 ` bonzini at gnu dot org
2015-12-18 21:32 ` joseph at codesourcery dot com
2015-12-18 21:32 ` carlos at redhat dot com
2015-12-18 21:32 ` carlos at redhat dot com
2024-01-08 10:37 ` maiku.fabian at gmail dot com
2024-01-08 10:43 ` maiku.fabian at gmail dot com
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=bug-19376-716-nJSRiJ4cyb@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.org \
/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).