Thomas Morley <thomasmorle...@gmail.com> writes: >> Processing `./c0/lily-c236818d.ly' >> Parsing... >> Renaming input to: `/home/hermann/lilypond-git/input/regression/utf-8.ly' >> Interpreting music... >> Preprocessing graphical objects... >> Calculating line breaks... >> Drawing systems... >> Writing header field `texidoc' to `./c0/lily-c236818d.texidoc'... >> Writing ./c0/lily-c236818d-1.signature >> Writing ./c0/lily-c236818d-2.signature >> Layout output to `./c0/lily-c236818d.eps'... >> Converting to `./c0/lily-c236818d.pdf'... >> warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4 >> -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite >> -sOutputFile=./c0/lily-c236818d.pdf -c.setpdfwrite >> -f./c0/lily-c236818d.eps)' failed (256) >> >> Every problematic file listed in the log compiles on its own without >> problem. They all deal with fonts in some way, though.
I think make doc uses --bigpdf and some sort of PDF postprocessing. Maybe one needs that to reproduce? -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
