lilypond-user
[Top][All Lists]
Advanced

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

Re: lilypond 2.19.20 fails to compile


From: N. Andrew Walsh
Subject: Re: lilypond 2.19.20 fails to compile
Date: Tue, 28 Apr 2015 21:22:37 +0200

--verbose gives me:
 $ lilypond --verbose transkription\ kayser\ 1.\ messe\ c-dur.ly 
Log level set to 287
GNU LilyPond 2.19.20
Relocation: from PATH=/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4:/opt/android-sdk-update-manager/tools:/opt/android-sdk-update-manager/platform-tools:/usr/games/bin
argv0=lilypond
PATH=/usr/bin (prepend)
Setting PATH to /usr/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4:/opt/android-sdk-update-manager/tools:/opt/android-sdk-update-manager/platform-tools:/usr/games/bin
Relocation: compile datadir=, new datadir=/usr/share/lilypond//2.19.20
Relocation: framework_prefix=/usr/bin/..
Setting INSTALLER_PREFIX to /usr/bin/..
PATH=/usr/bin/../bin (prepend)
Setting PATH to /usr/bin/../bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4:/opt/android-sdk-update-manager/tools:/opt/android-sdk-update-manager/platform-tools:/usr/games/bin
Setting GUILE_MIN_YIELD_1 to 65
Setting GUILE_MIN_YIELD_2 to 65
Setting GUILE_MIN_YIELD_MALLOC to 65
Setting GUILE_INIT_SEGMENT_SIZE_1 to 10485760
Setting GUILE_MAX_SEGMENT_SIZE to 104857600

LILYPOND_DATADIR="/usr/share/lilypond/2.19.20"
LOCALEDIR="/usr/share/locale"

Effective prefix: "/usr/share/lilypond/2.19.20"
GUILE_LOAD_PATH="/usr/share/guile/1.8"
PATH="/usr/bin/../bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4:/opt/android-sdk-update-manager/tools:/opt/android-sdk-update-manager/platform-tools:/usr/games/bin"
[/usr/share/lilypond/2.19.20/scm/lily.scm]
Guile 1.8
[/usr/share/lilypond/2.19.20/scm/lily-library.scm]
[/usr/share/lilypond/2.19.20/scm/output-lib.scm]
[/usr/share/lilypond/2.19.20/scm/markup-macros.scm]
[/usr/share/lilypond/2.19.20/scm/parser-ly-from-scheme.scm]
[/usr/share/lilypond/2.19.20/scm/file-cache.scm]
[/usr/share/lilypond/2.19.20/scm/define-event-classes.scm]
[/usr/share/lilypond/2.19.20/scm/define-music-callbacks.scm]
[/usr/share/lilypond/2.19.20/scm/define-music-types.scm]
[/usr/share/lilypond/2.19.20/scm/define-note-names.scm]
[/usr/share/lilypond/2.19.20/scm/c++.scm]
[/usr/share/lilypond/2.19.20/scm/chord-entry.scm]
[/usr/share/lilypond/2.19.20/scm/skyline.scm]
[/usr/share/lilypond/2.19.20/scm/markup.scm]
[/usr/share/lilypond/2.19.20/scm/define-markup-commands.scm]
[/usr/share/lilypond/2.19.20/scm/stencil.scm]
[/usr/share/lilypond/2.19.20/scm/modal-transforms.scm]
[/usr/share/lilypond/2.19.20/scm/chord-generic-names.scm]
[/usr/share/lilypond/2.19.20/scm/chord-ignatzek-names.scm]
[/usr/share/lilypond/2.19.20/scm/music-functions.scm
[/usr/share/lilypond/2.19.20/scm/define-music-display-methods.scm]
]
[/usr/share/lilypond/2.19.20/scm/part-combiner.scm]
[/usr/share/lilypond/2.19.20/scm/autochange.scm]
[/usr/share/lilypond/2.19.20/scm/define-music-properties.scm]
[/usr/share/lilypond/2.19.20/scm/time-signature.scm]
[/usr/share/lilypond/2.19.20/scm/time-signature-settings.scm]
[/usr/share/lilypond/2.19.20/scm/auto-beam.scm]
[/usr/share/lilypond/2.19.20/scm/chord-name.scm]
[/usr/share/lilypond/2.19.20/scm/bezier-tools.scm]
[/usr/share/lilypond/2.19.20/scm/ly-syntax-constructors.scm]
[/usr/share/lilypond/2.19.20/scm/define-context-properties.scm]
[/usr/share/lilypond/2.19.20/scm/translation-functions.scm]
[/usr/share/lilypond/2.19.20/scm/script.scm]
[/usr/share/lilypond/2.19.20/scm/midi.scm]
[/usr/share/lilypond/2.19.20/scm/layout-beam.scm]
[/usr/share/lilypond/2.19.20/scm/parser-clef.scm]
[/usr/share/lilypond/2.19.20/scm/layout-slur.scm]
[/usr/share/lilypond/2.19.20/scm/font.scm]
[/usr/share/lilypond/2.19.20/scm/encoding.scm]
[/usr/share/lilypond/2.19.20/scm/bar-line.scm]
[/usr/share/lilypond/2.19.20/scm/flag-styles.scm]
[/usr/share/lilypond/2.19.20/scm/fret-diagrams.scm]
[/usr/share/lilypond/2.19.20/scm/tablature.scm]
[/usr/share/lilypond/2.19.20/scm/harp-pedals.scm]
[/usr/share/lilypond/2.19.20/scm/define-woodwind-diagrams.scm]
[/usr/share/lilypond/2.19.20/scm/display-woodwind-diagrams.scm]
[/usr/share/lilypond/2.19.20/scm/predefined-fretboards.scm]
[/usr/share/lilypond/2.19.20/scm/define-grob-properties.scm]
[/usr/share/lilypond/2.19.20/scm/define-grobs.scm]
[/usr/share/lilypond/2.19.20/scm/define-grob-interfaces.scm]
[/usr/share/lilypond/2.19.20/scm/define-stencil-commands.scm]
[/usr/share/lilypond/2.19.20/scm/scheme-engravers.scm]
[/usr/share/lilypond/2.19.20/scm/titling.scm]
[/usr/share/lilypond/2.19.20/scm/text.scm]
[/usr/share/lilypond/2.19.20/scm/paper.scm]
[/usr/share/lilypond/2.19.20/scm/backend-library.scm]
[/usr/share/lilypond/2.19.20/scm/x11-color.scm]
[/usr/share/lilypond/2.19.20/scm/safe-lily.scm]
Initializing FontConfig...
Adding font directory: /usr/share/lilypond/2.19.20/fonts/otf
Building font database...

Processing `transkription kayser 1. messe c-dur.ly'
Parsing...
[/usr/share/lilypond/2.19.20/ly/init.ly
[<string>
 [/usr/share/lilypond/2.19.20/ly/declarations-init.ly
  [/usr/share/lilypond/2.19.20/ly/music-functions-init.ly]
  [/usr/share/lilypond/2.19.20/ly/toc-init.ly]
Using `nederlands' note names...
  [/usr/share/lilypond/2.19.20/ly/drumpitch-init.ly]
  [/usr/share/lilypond/2.19.20/ly/chord-modifiers-init.ly]
  [/usr/share/lilypond/2.19.20/ly/script-init.ly]
  [/usr/share/lilypond/2.19.20/ly/chord-repetition-init.ly]
  [/usr/share/lilypond/2.19.20/ly/scale-definitions-init.ly]
  [/usr/share/lilypond/2.19.20/ly/dynamic-scripts-init.ly]
  [/usr/share/lilypond/2.19.20/ly/spanners-init.ly]
  [/usr/share/lilypond/2.19.20/ly/predefined-fretboards-init.ly]
  [/usr/share/lilypond/2.19.20/ly/string-tunings-init.ly]
  [/usr/share/lilypond/2.19.20/ly/property-init.ly]
  [/usr/share/lilypond/2.19.20/ly/grace-init.ly]
  [/usr/share/lilypond/2.19.20/ly/midi-init.ly
   [/usr/share/lilypond/2.19.20/ly/performer-init.ly]]
  [/usr/share/lilypond/2.19.20/ly/paper-defaults-init.ly
   [/usr/share/lilypond/2.19.20/ly/titling-init.ly]
   [/usr/share/lilypond/2.19.20/ly/text-replacements.ly]]
  [/usr/share/lilypond/2.19.20/ly/context-mods-init.ly]
  [/usr/share/lilypond/2.19.20/ly/engraver-init.ly
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly]]
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly]]
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly]]
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly
[/usr/share/lilypond/2.19.20/ly/music-functions-init.ly]]]]]
Using `nederlands' note names...
 [transkription kayser 1. messe c-dur.ly
  [transkription kayser 1. messe c-dur - kyrie.ly
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]]
transkription kayser 1. messe c-dur.ly:88:10: error: cannot find file: `openlilylib'
(search path: `/usr/share/lilypond/2.19.20/fonts/svg/:/usr/share/lilypond/2.19.20/fonts/type1/:/usr/share/lilypond/2.19.20/fonts/otf/:/usr/share/lilypond/2.19.20/scm:/usr/share/lilypond/2.19.20/ps:/usr/share/lilypond/2.19.20/ly:')
\include 
         "openlilylib"
transkription kayser 1. messe c-dur.ly:90:1: error: unknown escaped string: `\useLibrary'

\useLibrary Scholarly
transkription kayser 1. messe c-dur.ly:92:1: error: unknown escaped string: `\useModule'

\useModule scholarly.annotate
]
transkription kayser 1. messe c-dur.ly:92:30: error: syntax error, unexpected end of input, expecting '='
\useModule scholarly.annotate
                             
Interpreting music...
[/usr/share/lilypond/2.19.20/fonts/otf/emmentaler-20.otf]
[/usr/share/lilypond/2.19.20/fonts/otf/emmentaler-11.otf]
[/usr/share/lilypond/2.19.20/fonts/otf/emmentaler-13.otf]
[/usr/share/lilypond/2.19.20/fonts/otf/emmentaler-14.otf][8][16][24][32]
elapsed time: 0.17 seconds
Element count 4651 (spanners 294) 
Preprocessing graphical objects...
Grob count 7049
[linux_libertine_g_2.8212890625]
[emmentaler-13_4.5693359375]
[linux_libertine_g_italic_1.5830078125]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[transkription kayser 1. messe c-dur.ly]
[emmentaler-11_3.6259765625]
[linux_libertine_g_2.5126953125]
[linux_biolinum_g_3.9892578125]
[linux_libertine_g_italic_2.662109375]
Interpreting music...
elapsed time: 0.36 seconds
MIDI output to `transkription kayser 1. messe c-dur.midi'...Track... 
[0]
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
[14]
[15]
[linux_libertine_g_3.166015625]
[linux_libertine_g_italic_4.4775390625]
[linux_libertine_g_7.1083984375]
[linux_libertine_g_4.4775390625]
Finding the ideal number of pages...
Fitting music on 1 or 2 pages...
Drawing systems...
Element count 3501
[linux_libertine_g_italic_2.5126953125]
[linux_libertine_g_2.98828125]
[/usr/share/lilypond/2.19.20/fonts/otf/emmentaler-brace.otf]
Layout output to `transkription kayser 1. messe c-dur.ps'...
[/usr/share/lilypond/2.19.20/fonts/otf/emmentaler-11.otf]
[/usr/share/lilypond/2.19.20/fonts/otf/emmentaler-13.otf]
[/usr/share/fonts/libertine-g/LinBiolinum_R_G.ttf]
[/usr/share/fonts/libertine-g/LinLibertine_R_G.ttf]
[/usr/share/fonts/libertine-g/LinLibertine_RI_G.ttf]
[/usr/share/lilypond/2.19.20/ps/music-drawing-routines.ps]
[/usr/share/lilypond/2.19.20/ps/lilyponddefs.ps]
Converting to `./transkription kayser 1. messe c-dur.pdf'...
Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./transkription kayser 1. messe c-dur.pdf -c.setpdfwrite -ftranskription kayser 1. messe c-dur.ps'...

GPL Ghostscript 9.15 (2014-09-22)
Copyright (C) 2014 Artifex Software, Inc.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Error: /undefinedresult in --glyphshow--
Operand stack:
   0.5778   91.6354   -11.8188   space
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1951   1   3   %oparray_pop   1950   1   3   %oparray_pop   1934   1   3   %oparray_pop   1820   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   0   --nostringval--   %repeat_continue   --nostringval--
Dictionary stack:
   --dict:1186/1684(ro)(G)--   --dict:0/20(G)--   --dict:110/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 14321120
GPL Ghostscript 9.15: Unrecoverable error, exit code 1
warning: `(gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./transkription kayser 1. messe c-dur.pdf -c.setpdfwrite -ftranskription kayser 1. messe c-dur.ps)' failed (256)

programming error: Parsed object should be dead: #<Grob LyricHyphen >
continuing, cross fingers
programming error: Parsed object should be dead: #<Context_def Staff transkription kayser 1. messe c-dur - kyrie.ly:295:3>
continuing, cross fingers
programming error: Parsed object should be dead: #<Prob: paper-system C++: Prob((Y-offset . 20.1738061450481) (system-grob . #<Grob System >) (staff-refpoint-extent -5.73848092065415 . -5.73848092065415) (last-in-score . #t) (page-turn-penalty) (page-break-penalty) (page-turn-permission . allow) (page-break-permission . allow) (vertical-skylines . #<Skyline_pair>) (stencil . #<Stencil>))() >

continuing, cross fingers
fatal error: failed files: "transkription kayser 1. messe c-dur.ly"
------------------------------------------------
You are correct: it seems to be an issue with ghostscript. Any ideas on a workaround?

Cheers,

A
PS, sorry for the wall-o

On Tue, Apr 28, 2015 at 9:14 PM, Urs Liska <address@hidden> wrote:
Could you please post the end of the output of running with --verbose?

This *reminds* me of a problem I recently had that was/is related to a change in Ghostscript handling.

Am 28.04.2015 um 21:03 schrieb N. Andrew Walsh:
Hi All,

I'm not sure if this is the place to post about recent versions and possible bugs. I get the following error when trying to compile a MWE:

Starting lilypond 2.19.20 [Untitled]...

Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'

Parsing...

Interpreting music...

Preprocessing graphical objects...

Finding the ideal number of pages...

Fitting music on 1 page...

Drawing systems...

Layout output to `document.ps'...

Converting to `./document.pdf'...

warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -fdocument.ps)' failed (256)


programming error: Parsed object should be dead: #<Grob NoteSpacing >

continuing, cross fingers

programming error: Parsed object should be dead: #<Prob: paper-system C++: Prob((Y-offset . 1.0) (system-grob . #<Grob System >) (staff-refpoint-extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-break-penalty) (page-turn-permission . allow) (page-break-permission . allow) (vertical-skylines . #<Skyline_pair>) (stencil . #<Stencil>))() >


continuing, cross fingers

fatal error: failed files: "/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly"

Exited with return code 1.


MWE was:

\version "2.19.20"


\relative c' {

a4 b c d

}


I get the same errors on more complex files, so I'm guessing it's something deeper than the level of file syntax. 


But then, this is the dev version of lilypond, so stuff like this is probably expected?


Should this be sent to lilypond-dev?


Cheers,


A



_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user


_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user



reply via email to

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