lilypond-user
[Top][All Lists]
Advanced

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

Re: 64-bit Mac build of 2.20 is now available!


From: Marnen Laibow-Koser
Subject: Re: 64-bit Mac build of 2.20 is now available!
Date: Tue, 17 Mar 2020 18:07:13 -0400

On Tue, Mar 17, 2020 at 5:35 PM Arle Lommel <address@hidden> wrote:
Two bugs pop up in the default install.

#1. Use of the wrong encoding for the file system.

I previously reported it on Hans Åberg’s installer.

The build seems to expect file names to use ISO Latin-1 rather than UTF-8, so if you use characters outside of the 7-bit range in your directory tree or file names, you get crashes where Lilypond cannot save the results after processing the file.  A log looks like this:

Starting lilypond 2.20.0 [Bartók-Béla-Székely-friss.ly]...
Processing `/Users/fenevad/Dropbox/music scores/bartok/Bartók-Béla-Székely-friss.ly'
Parsing...
Interpreting music...[8][16][24][32][40][40]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 3 or 4 pages...
Drawing systems...
Layout output to `/var/folders/64/hl6gpmy17994gn1w87__6yvc0000gn/T//lilypond-7Vi2o3'...
Converting to `Bartók-Béla-Székely-friss.pdf'...
warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -dAutoRotatePages=/None -dPrinted=false -sOutputFile=Bartók-Béla-Székely-friss.pdf -c.setpdfwrite -f/var/folders/64/hl6gpmy17994gn1w87__6yvc0000gn/T//lilypond-7Vi2o3)' failed (256)

fatal error: failed files: "/Users/fenevad/Dropbox/music scores/bartok/Barto�\x81k-Be�\x81la-Sze�\x81kely-friss.ly"
Exited with return code 1.

You can see the problem in the second-to-last line. If I change the file name to lose the non-ASCII characters, it works fine.

Hans reported the following as a solution:

I believe this is bug in the software that LilyPond depends on, MacOS sets LC_CTYPE=UTF-8, and does not set LANG.

I use a script to call it from named ‘lilypond', which can be put in /usr/local/bin/lilypond:
export LC_CTYPE=en_US.UTF-8
export LANG=en_US.UTF-8
exec /opt/lilypond/bin/lilypond "$@“

It can be created and installed as follows: In Terminal write (^D is <control D>)
% cat > lilypond
export LC_CTYPE=en_US.UTF-8
export LANG=en_US.UTF-8
exec /opt/lilypond/bin/lilypond "$@“
^D

% chmod a+x lilypond
% sudo -s cp lilypond /usr/local/bin/lilypond

And 'rm lilypond' if you do not want to keep the script.

Ideally the executables would solve the problem without an external script.

Thanks, this makes sense.  I should be able to set the variables correctly (and actually, the lilypond "binary" in the app bundle is already a script that sets a few variables and calls the real executable, so putting a few more in there should not be a problem).   

I've created https://gitlab.com/marnen/lilypond-mac-builder/-/issues/23 for this bug.  Feel free to subscribe there for updates, or to create new issues there if they're problems with the 64-bit Mac packaging rather than LilyPond itself.


#2: Update.ly doesn’t work for me when invoked from Frescobaldi.

You mean convert-ly?
 
I get this message about a bad CPU type when I run it from Frescobaldi.

Weird, I haven't seen that.  I'll try to reproduce.  What version of Mac OS are you running?

Best,
--
Marnen Laibow-Koser
address@hidden
http://www.marnen.org

PNG image


reply via email to

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