Hello Stu,

here you see two messages: One is that your file did fail to compile. The other 
one is a note that the version string is older than your Lilypond version, and 
a suggestion that this might be the cause. From your messages you are clearly 
compiling a 2.25.18 file with 2.25.21, so this explains why you get that 
message. It is quite unlikely though that this minor version difference broke 
your file.

Instead if you look into the output Lilypond should give you a hint. In the 
code you send for example you clearly see the error messages

<PathSource>/2024-11-18_MessageCompilationFailedSimple.ly:3:10: error: 
cannot find file: `../../NonExistent.ly'

Note that having an error does not necessarily prevent Lilypond from compiling 
the file. Not finding an include is such a case. Lilypond will give an error 
and 
eventually stop with code 1, but before it will still try to compile the score 
as is. As similar behaviour can be seen simply by giving a future version 
string or even just omiting minor version for unstable.

It is not really possible to further diagnose the issue without having the 
actual output of your file.

Cheers,
Valentin

Am Montag, 18. November 2024, 19:40:11 MEZ schrieb Stu McKenzie via LilyPond 
User List:
> The  message appeared during processing of a score, and provides no
> indication of where the culprit is.
> 
> I verified that all of my source files have the correct version number
> (\version "2.25.18").
> 
> It would be helpful if the message identified the file causing the error.
> 
> I searched for this message in the LilyPond code, and found 8 files
> contain the same message. (The list of files is at the end of this post).
> 
> This message didn't help me to identify the file causing the error, so
> I've no idea what was causing the error.
> 
> How do I find out which file caused the error?

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to