From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] media-libs/babl-0.1.96-r1 compile dies during emerge @world
Date: Mon, 12 Dec 2022 08:49:12 +0000 [thread overview]
Message-ID: <2265601.ElGaqSPkdT@lenovo.localdomain> (raw)
In-Reply-To: <Y5bmfqqGDjHQLNKZ@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Monday, 12 December 2022 08:29:50 GMT Walter Dnes wrote:
> On Mon, Dec 12, 2022 at 09:00:42AM +0100, netfab wrote
>
> > Le 12/12/22 à 07:30, Walter Dnes a tapoté :
> > > I don't think they should make any difference, but included for
> > >
> > > completeness. File-attached is the gzipped build log...
> > >
> > > (vapigen-0.56:375): GLib-CRITICAL **: 00:58:53.271: PCRE library is
> > > compiled without UTF8 support
> >
> > You should try to first upgrade/rebuild the dev-libs/glib package.
> >
> > https://bugs.gentoo.org/883877
>
> No change. dev-libs/glib-2.74.1-r1:2::gentoo was a straight rebuild;
> no upgrade; no USE-flag changes; and the babl compile still dies. What
> is the "GLib-CRITICAL" bit about PCRE with no UTF8 support?
I don't know about the UTF8 error and if it is related to your failure, but
since it complains about the vala compiler, it may be worth rebuilding it
first?
emerge -1aDv dev-lang/vala
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-12 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 6:30 [gentoo-user] media-libs/babl-0.1.96-r1 compile dies during emerge @world Walter Dnes
2022-12-12 8:00 ` netfab
2022-12-12 8:29 ` Walter Dnes
2022-12-12 8:49 ` Michael [this message]
2022-12-12 23:14 ` Walter Dnes
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=2265601.ElGaqSPkdT@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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