From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] libglib2: the system PCRE needs to have UTF and UCP enabled
Date: Mon, 25 Nov 2013 11:04:00 +0100 [thread overview]
Message-ID: <87pppolrvz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1385373282.2810.8.camel@sven> (Sven Neumann's message of "Mon, 25 Nov 2013 10:54:42 +0100")
>>>>> "Sven" == Sven Neumann <neumann@teufel.de> writes:
Hi,
>> Hmm, ok - That wasn't completely clear to me. So even though it's
>> just a warning, this is something critical?
> Any functionality that use GRegex won't work if the system PCRE is not
> compiled with UTF-8 and UCP support. There might be glib-based
> applications that won't be affected by this, but there is a good chance
> that people will run into unexpected problems because of this.
Ok, thanks for the details.
>> When was this introduced? By the 2.36.1 -> 2.36.3 bump or is 2013.08
>> also affected?
> As far as I can see this was introduced with commit fe192908a4e:
> commit fe192908a4e3195b6f724310fe83fadaf18b66e7
> Author: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Date: Sat Mar 9 08:21:30 2013 +0000
> libglib2: use system pcre when available
Ok, so 2013.08 is also affected. We afaik didn't have any bug reports
related to this, but I have added the 2 patches for 2013.11 - Thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-11-25 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 21:58 [Buildroot] [PATCH v2 2/2] libglib2: the system PCRE needs to have UTF and UCP enabled Sven Neumann
2013-11-22 22:33 ` Peter Korsgaard
2013-11-25 7:49 ` Sven Neumann
2013-11-25 9:17 ` Peter Korsgaard
2013-11-25 9:54 ` Sven Neumann
2013-11-25 10:04 ` Peter Korsgaard [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=87pppolrvz.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.