bug-lilypond
[Top][All Lists]
Advanced

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

Re: Scale example not compiled on Mac OS X 10.9.5


From: Simon Albrecht
Subject: Re: Scale example not compiled on Mac OS X 10.9.5
Date: Mon, 24 Aug 2015 20:22:31 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0

Am 24.08.2015 um 18:27 schrieb David Kastrup:
Simon Albrecht <address@hidden> writes:

Hello Anita,

sorry, but I can’t quite figure out what your problem is. You say ‘not
compiled’ in the subject, but actual message suggests that the output
is different from what you expected. Please give us the actual code
and output (as attachments) and describe the exact problem.
I guess that you mean the Welcome_to_LilyPond.ly file from the 2.18.2
install?
Indeed, it compiles fine and with the exact results I’d expect if I
use 2.18.2; however, the \version statement says 2.16.0 and with
2.16.2 it fails, with the following log:

Starting lilypond 2.16.2 [Welcome_to_LilyPond.ly]...

Processing
`/home/simon/lilypond/2.18.2/lilypond/usr/share/lilypond/current/ly/Welcome_to_LilyPond.ly'

Parsing...

/home/simon/lilypond/2.18.2/lilypond/usr/share/lilypond/current/ly/init.ly:9:1
<0>: error: GUILE signaled an error for the expression beginning here
I am not really surprised that you are not successful running the
executable for LilyPond 2.16.2 with the init.ly file from LilyPond
2.18.2.
Well, I only tried to figure out what it _might_ have been that the OP did, in order to be any help. When I opened the ly/Welcome_to_Lilypond.ly file from the 2.18.2 installation (which has \version "2.16.0" at the beginning) in Frescobaldi and had it compiled, the automatic version selection of Frescobaldi used 2.16.2, which then did not recur on it’s own init.ly, but on the 2.18.2 one from the directory of the file being processed. That _might_ have been the OP’s problem. It seems that she is not a very experienced user (and not very comfortable with English) and thus has difficulties to describe the problem.

Yours sincerely, Simon



reply via email to

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