On 2025-09-22 10:36, Martin Tarenskeen wrote:
Op maandag 22 september 2025 om 08:18:38 +02:00:00 schreef Mats Behre
<[email protected]>:
But as you can see from the logs Lilypond itself works fine, the problem comes
when it's about to create the output file.
Are you writing the output file to a writable location? I am not a Mac user,
just guessing...
Maybe try to write to another location using the option -o
/full/path/to/a/user/writable/location/output.pdf on the commandline? (don't
take that pathname literally, but you know what I mean :-)
Martin
I managed to solve this by adding .../lilypond/libexec (where Python is) to
PATH. Either Lilypond is using a relative path and that's not allowed anymore
unless it's in PATH, or it has used some other way to find Python that doesn't
work anymore ...
Mats
