-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Labels
Description
On my PC the example fails on the XeLaTeX part, but I can't see whether it is related to the snippet or to my installation.
The log is:
This is XeTeX, Version 3.14159265-2.6-0.99996 (TeX Live 2016/Debian) (preloaded format=xelatex)
restricted \write18 enabled.
entering extended mode
pdftops: /home/uliska/software/lilypond/releases/2.19.60/usr/lib/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by pdftops)
pdftops: /home/uliska/software/lilypond/releases/2.19.60/usr/lib/libjpeg.so.62: no version information available (required by /lib/x86_64-linux-gnu/libpoppler.so.64)
pdftops: /home/uliska/software/lilypond/releases/2.19.60/usr/lib/libtiff.so.5: no version information available (required by /lib/x86_64-linux-gnu/libpoppler.so.64)
pdftops: /home/uliska/software/lilypond/releases/2.19.60/usr/lib/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /lib/x86_64-linux-gnu/libpoppler.so.64)
pdftops: /home/uliska/software/lilypond/releases/2.19.60/usr/lib/libz.so.1: no version information available (required by /lib/x86_64-linux-gnu/libpng16.so.16)
fatal error: cannot find file: `xelatex-20170710145823-1.eps' (load path: `/home/uliska/software/lilypond/releases/2.19.60/usr/share/lilypond/current/fonts/svg/:/home/uliska/software/lilypond/releases/2.19.60/usr/share/lilypond/current/fonts/type1/:/home/uliska/software/lilypond/releases/2.19.60/usr/share/lilypond/current/fonts/otf/:/home/uliska/software/lilypond/releases/2.19.60/usr/share/lilypond/current/scm:/home/uliska/software/lilypond/releases/2.19.60/usr/share/lilypond/current/ps:/home/uliska/software/lilypond/releases/2.19.60/usr/share/lilypond/current/ly:/home/uliska/git/bfsc/projects/fried/das-trunkne-lied:/home/uliska/git/bfsc/projects/fried/das-trunkne-lied/library/ly:/home/uliska/git/bfsc/projects/fried/das-trunkne-lied/library/ly/empty-segments:/home/uliska/git/oll-lib/snippets:/home/uliska/git/oll-lib/snippets/ly:/home/uliska/git/oll-lib:')
The last message is from LilyPond again, but obviously a consequence of the previous fail.
Reactions are currently unavailable