[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: a new way to build LilyPond binary releases

From: Mats Bengtsson
Subject: Re: a new way to build LilyPond binary releases
Date: Thu, 12 Mar 2020 16:22:38 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1

On 2020-03-12 16:17, Mats Bengtsson wrote:

On 2020-03-12 14:39, Jonas Hahnfeld wrote:
I did test some more advanced files than "{ c' }", but apparently not
complicated enough. I think this one actually has the same root case as
Karlin reported: I traced this back to the garbage collector freeing
objects prematurely. Apparently it's not really happy that I made it
unaware of threading...
I've just finished building anew, please give a
try. Or rebuild with the updated scripts 😉

I did a quick test of the lilypond-linux-x86_64-full.tar.gz version on a reasonably large project (some 80+ page output string quartet score) and it runs without any error messages and produces correct output, with the exception of Unicode characters in titling that are completely garbled, but that's perhaps a known issue.

When untarring the package, I happened to notice that the tar ball contains a number of soft links to /home/jonas/lilypond-binaries/dependencies/install/fontconfig-2.13.1/...

I just spotted another oddity towards the end of the log printouts that probably also is related to the Guile updates:

"Finding the ideal number of pages...Omitting the destination on a call to format is deprecated.
Pass #f as the destination, before the format string.

Fitting music on 84 or 85 pages..."


reply via email to

[Prev in Thread] Current Thread [Next in Thread]