Re: Fwd: Compile of glycin failed

"nicP" ([email protected] via blfs-support Mailing List) <[email protected]> Tue, 24 Mar 2026 09:55:28 +0100
Newsgroups gmane.linux.lfs.beyond.support
Message-ID <[email protected]>
This is a multi-part message in MIME format...

------------=_1774342550-1253-18528
Content-Language: fr
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Le 24/03/2026 =C3=A0 09:08, Rainer Fiebig a =C3=A9crit=C2=A0:
> Am 24.03.26 um 01:25 schrieb Stephan Hunker ([email protected]
> via blfs-support Mailing List):
>> On Fri, Mar 20, 2026 at 8:12=E2=80=AFAM Manfred Hahn <
>> [email protected]> wrote:
>>
>>> ---------- Forwarded message ---------
>>> Von: Manfred Hahn <[email protected]>
>>> Date: Fr., 20. M=C3=A4rz 2026 um 15:07 Uhr
>>> Subject: Compile of glycin failed
>>> To: <[email protected]>
>>>
>>>
>>>> Hi,
>>>
>>>> On my way to gtk3 I'm stuck compiling glycin. Logfile attached.
>>>> The mentioned command 'rustc -vV' works on the command line and gives
>>>> the following output:
>>>
>>>> rustc 1.89.0 (29483883e 2025-08-04) (for BLFS 12.4)
>>>> binary: rustc
>>>> commit-hash: 29483883eed69d5fb4db01964cdf2af4d86e9cb2
>>>> commit-date: 2025-08-04
>>>> host: x86_64-unknown-linux-gnu
>>>> release: 1.89.0
>>>> LLVM version: 20.1.8
>>>
>>>> I can not determine the directory which cannot be used or created by
>>> meson.
>>>> Any help wellcome
>>>
>>> Compile now succeeded!
>>> What I did different:
>>> - compile in text mode (before in XWindow)
>>> - patches done in a separate step (before I had a batch file with all
>>> commands)
>>>
>>> Don't really know why this make a difference, but it works.
>>>
>>> Manfred
>>> --
>>> http://lists.linuxfromscratch.org/sympa/info/blfs-support
>>> Unsubscribe: See the above information page
>>>
>>
>> Interestingly, I ran into this issue as well on the path to building
>> lightdm (which requires Exo, which requires GTK, which requires
>> gdk-pixbuf). In BLFS 13.0, you have a circular dependency with glycin, in
>> which you have to build gdk twice - once before, and once after installi=
ng
>> glycin.
>>
>> When I tried to install glycin, I got the error you described. I could n=
ot
>> figure out how to fix it at the time (I was also in an X session, icewm =
at
>> the time using xterm).
>>
>> I realized that in BLFS 12.4, glycin is not required for gdk-pixbuf, so =
my
>> workaround was to install the prior version of gdk-pixbuf, 2.42.12. This
>> worked great.
>=20
> Glycin is not strictly "required" for gdk-pixbuf, only "recommended".
> You could build gdk-pixbuf without glycin by using option
>=20
> 	-Dglycin=3Ddisabled   	\
>=20
> The description for glycin is "The glycin package contains a sandboxed
> and extendable image loading framework."  Well, whatever that means, I
> never needed it.
>=20
> Rainer
>=20
True. But with gdk-pixbuf built without glycin, gtkmm-3.24.10 failed to=20
build. I didn't keep record of the errors reported, but they were=20
related to gdk-pixbuf.

When I rebuilt gdk-pixbuf with glycin, gtkmm compilation was OK.
--=20
nicP
LFS ID 13025



------------=_1774342550-1253-18528
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-support
Unsubscribe: See the above information page

------------=_1774342550-1253-18528--