lilypond-user
[Top][All Lists]
Advanced

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

Re: Exited with return code 1. - Guile signal error & cannot find contex


From: Ben
Subject: Re: Exited with return code 1. - Guile signal error & cannot find context to switch to
Date: Thu, 28 Sep 2017 21:04:45 -0400
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

On 9/28/2017 8:43 PM, MING TSANG wrote:
Dear lilyponders,
I run (compile) the attached test-tempo.ly and receive the following error (Exited with return code 1.)
However, the pdf output seems OK.
Ming


Starting lilypond-windows.exe 2.19.65 [test-tempo.ly]...
Processing `C:/Users/user/AppData/Local/Temp/frescobaldi-t7bi8umh/tmp4uf0oy18/test-tempo.ly'
Parsing...
programming error: Unknown type predicate
continuing, cross fingers
C:/Users/user/AppData/Local/Temp/frescobaldi-t7bi8umh/tmp4uf0oy18/test-tempo.ly:152:43: error: GUILE signaled an error for the _expression_ beginning here
\set Score.tempoWholesPerMinute = #
(ly:make-moment 76 4.)

\rehearsalMidi "soprano" "soprano sax" \verseSopranoVoice

Interpreting music...
warning: type check for `tempoWholesPerMinute' failed; value `#<unspecified>' must be of type `moment'
\change Staff = "right" bf8 df' gf' bf'4 g'8) |}

lft.44 = {
\change Staff = "left" ef,8( bf, ef

\change Staff = right gf8 bf df' <gf'ef''>4.) |}


MIDI output to `test-tempo-ten.mid'...
Interpreting music...
Preprocessing graphical objects...
Interpreting music...
MIDI output to `test-tempo.mid'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `./tmp-lilypond-pTm2Ng'...
Converting to `test-tempo.pdf'...
Deleting `./tmp-lilypond-pTm2Ng'...
Wrong type argument in position 2 (expecting unknown type): 4.0
Wrong type argument in position 2 (expecting unknown type): 4.0
fatal error: failed files: "C:\\Users\\user\\AppData\\Local\\Temp\\frescobaldi-t7bi8umh\\tmp4uf0oy18\\test-tempo.ly"

Hi Ming,

I didn't see any attached files with this message, just a heads up.


reply via email to

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