for example create a file "lines.ly" with a minimal content
\version "2.19.19"
{c' d' e' f'}
and compile ...
I'm trying to narrow down the issue
It seems that on some systems (like mine).
# gs lines.ps
is expanded to something like
# gs /usr/share/ghostscript/9.15/lines.ps
but
# gs /complete/path/to/lines.ps
is not.
When compiling a lines.ly file, lines.ps is produced as an intermediate
file before ghostscript converts this to lines.pdf
The bug would be fixed if lilypond would make ghostscript use a complete
path to the intermediate lines.ps file for the ps to pdf conversion.
--
MT
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
