lilypond-devel
[Top][All Lists]
Advanced

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

make doc still fails - problem with lilypond-book - was: Still cannot ma


From: Thomas Morley
Subject: make doc still fails - problem with lilypond-book - was: Still cannot make doc
Date: Thu, 2 Jun 2016 23:10:38 +0200

First the good news.
With a build from a checkout of recent staging, I can successfully run
make LANGS='' doc
without any failure for orchestra.ly
... as soon as I comment/delete all japanese !!

But it allways fails for any japanese in the doc.
I spent some time to boil it down to a minmal example:

Doing
lilypond-book --output=out --pdf aaa-lilybook.lytex
on
%%%%%%% start of aaa-lilybook.lytex

\documentclass[a4paper]{article}

\begin{document}

\begin{lilypond}
\markup {
  %foo bar buzz
  いろはにほへど ちりぬるを
}

\end{lilypond}

\end{document}

%%%%%%% end of aaa-lilybook.lytex

always fails with:

$ lilypond-book --output=out --pdf aaa-lilybook.lytex
lilypond-book (GNU LilyPond) 2.19.43
Reading aaa-lilybook.lytex...
Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default page settings.

Dissecting...
Writing snippets...
Processing...
Running lilypond...
GNU LilyPond 2.19.43
Processing `./snippet-map--2641629851966957681.ly'
Parsing...
Processing `./55/lily-88e32432.ly'
Parsing...
Layout output to `./55/lily-88e32432.eps'...
Converting to `./55/lily-88e32432.pdf'...
warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
-dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
-sOutputFile=./55/lily-88e32432.pdf -c.setpdfwrite
-f./55/lily-88e32432.eps)' failed (256)

fatal error: failed files: "55/lily-88e32432.ly"
command failed: /home/hermann/lilypond-git/build/out/bin/lilypond
--formats=ps -dbackend=eps  -I  "./"  -I  "../" --formats=eps --pdf
-dinclude-eps-fonts -dgs-load-fonts  -deps-box-padding=3.000000
-dread-file-list -dno-strip-output-dir
"/home/hermann/lilypondH/Test/forum/aaa-doc-test/out/snippet-names--2641629851966957681.ly"
Child returned 1


But in a .ly-file

\markup {
  %foo bar buzz
  いろはにほへど ちりぬるを
}

always returns a correct pdf.

I'm on Ubuntu 16.04 64-bit

$ gs -v
GPL Ghostscript 9.18 (2015-10-05)

Output of
lilypond-git -dshow-available-fonts 2> available-fonts.log
is attached.


Anyone with an idea?


Thanks,
  Harm

Attachment: available-fonts.log
Description: Text Data


reply via email to

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