Re: Re: a new way to build LilyPond binary releases

[Jonas Hahnfeld]

Am Donnerstag, den 12.03.2020, 16:17 +0100 schrieb Mats Bengtsson:
> 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
> > https://github.com/hahnjo/lilypond-binaries/releases/tag/2020-03-12
> >  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.

Works for me, at least title = "äöüß" works. But maybe that is related
to the problem below...

> 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/...

Ouch, TIL: "cp -r" and "tar" preserve symlinks, at least on Linux. The
files are there in the packages for FreeBSD and zip archives can't
handle them, so mingw is also fine. As a temporary matter, I've
uploaded fontconfig-2.13.1-conf.tar.gz to the GitHub release. Could you
extract that to lilypond/etc/fonts/conf.d and overwrite the links?

Jonas

signature.asc
Description: This is a digitally signed message part