Re: LilyPond 2.23.6 released

[Omid Mo'menzadeh]

Sorry for cluttering the list, but the problem is actually with the way
FontConfig 2.13.94 is packaged on NixOS. I'll report it on their Github.
Thanks for the amazing work again.

On Wed, Feb 9, 2022 at 3:59 PM Omid Mo'menzadeh <omid.mnzadeh@gmail.com>
wrote:

> OK, it seems that I have found where the problem is. I built LilyPond
> against FontConfig 2.13.1, and it works just like the official binary. But
> the version built against FontConfig 2.13.94 and Guile 2.2 emits the same
> warning I mentioned. There seems to be some sort of soft incompatibility
> with FontConfig 2.13.94.
>
> On Wed, Feb 9, 2022 at 3:27 PM Omid Mo'menzadeh <omid.mnzadeh@gmail.com>
> wrote:
>
>> I can confirm that this is a packaging issue now. I patched the official
>> binary to see the glibc on my system, and it works without any warnings.
>> It's also considerably faster than my own compiled version (4.31s vs. 6.43s
>> on a single file).
>>
>> I suppose I should go on debugging this on my own, but asking for tips,
>> is there any difference in building with Guile 2.2 versus Guile 1.8, except
>> the Guile available on PATH?
>>
>> On Wed, Feb 9, 2022 at 12:56 PM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
>>
>>> Am Mittwoch, dem 09.02.2022 um 12:50 +0330 schrieb Omid Mo'menzadeh:
>>> > It works with Guile 2.2, but with a lot of the mentioned warnings.
>>> > The .nix files I attached describe a recipe for building LilyPond,
>>> > and two packages are built in the shell.nix file, so yes, I am
>>> > building both, using the same recipe, but one with Guile 1.8, and one
>>> > with Guile 2.2. Both are using the same FontConfig for sure.
>>>
>>> Thanks for clarifying.
>>>
>>> > The binaries under Nix are not really self-contained, so it would be
>>> > a challenge to create a binary. But I will try to isolate the issue.
>>>
>>> No, that's a misunderstanding. I'm asking if you could try the binaries
>>> that we provide, available for download from
>>> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1 on
>>> your system to see if that works.
>>>
>>