From: Sven Neumann <neumann@teufel.de>
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 08:49:34 +0100 [thread overview]
Message-ID: <1385365774.2810.1.camel@sven> (raw)
In-Reply-To: <87eh68nk15.fsf@dell.be.48ers.dk>
Hello,
On Fr, 2013-11-22 at 23:33 +0100, Peter Korsgaard wrote:
> >>>>> "Sven" == Sven Neumann <neumann@teufel.de> writes:
>
> > If glib2 is compiled with the system PCRE instead of the included
> > copy, then that system PCRE needs to have support for UTF-8 and
> > Unicode properties enabled. Otherwise you will get such warnings
> > at run-time:
>
> > GLib-CRITICAL **: PCRE library is compiled without UTF8 support
> > GLib-CRITICAL **: PCRE library is compiled without UTF8 properties support
>
> > Signed-off-by: Sven Neumann <neumann@teufel.de>
>
> Committed to next, thanks.
May I suggest that you also merge this to the stable tree. Otherwise
glib2 will be unusable on any system that also has pcre selected (which
is for example pulled in by gnutls).
Regards,
Sven
--
Sven Neumann
Senior System Architect
Lautsprecher Teufel GmbH
Gewerbehof B?lowbogen - Aufgang D1
B?lowstr. 66 - 10783 Berlin - Germany
Registernummer HRB 20271 beim Amtsgericht Berlin-Charlottenburg
Gesch?ftsf?hrer: Edgar van Velzen
Tel. +49 (0)30 - 300 930 - 0, Direkt -153
neumann at teufel.de
www.teufel.de www.teufelaudio.com http://blog.teufel.de
next prev parent reply other threads:[~2013-11-25 7:49 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 [this message]
2013-11-25 9:17 ` Peter Korsgaard
2013-11-25 9:54 ` Sven Neumann
2013-11-25 10:04 ` Peter Korsgaard
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=1385365774.2810.1.camel@sven \
--to=neumann@teufel.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox