On 2024-11-20 02:08, Valentin Petzel wrote:
Hello,
Am Dienstag, 19. November 2024, 18:05:00 MEZ schrieb Stu McKenzie via LilyPond
User List:
The above is the original post that I sent.
My original score was complicated, so I came up with the post that you
replied to (with 1 error and the message).
I’m well aware of that. But your original message did not contain any output.
The message "Note: compilation failed and \version outdated, did you
update input syntax with convert-ly? ", was the only message that was
reported to that score.
As I said the message appears if there are errors in the build, but not
because of the errors. The message in question does not know what exactly
causes the problems, it just sees: There have been problems with the run, and
the version of the score is older than the Lilypond version, so maybe that is
the problem?
If you get no other error messages then that is a problem of that specific
error, not of this warning message. Essentially this means there is something
in your file that causes Lilypond to fail that is not handled in a way such
that a message is printed. As I said, we cannot diagnose this any further at
this point without access to the actual log or optimally a score that has this
issue.
I'm trying to solve my original issue, which was that I couldn't
determine which \include caused the error message in my original score.
I was hoping that someone who knows the internals of LilyPond would
suggest that the source code could be changed to identify which file and
line was causing the error.
Maybe there's someone out there who can help?
I’m afraid, no. Do you use any custom functions or stuff? Or is your file basic
standard Lilypond?
Cheers,
Valentin
Thanks for your reply Valentin.
I had already replied to Knute Snortum that the convert-ly.py released
in 2.25.21 leaves the version as "2.25.18" and all of my files have the
statement [\version "2.25.18"].
In answer to your last point, I usually use a lot of custom "stuff" in
my includes that have been gathered from various sources. It seems that
there is conflict amongst them for this particular score.
It will take time to isolate the issue.
As I said in my previous post to David Wright, I've had to leave that
issue for now.
I'll return to it on another day, and try removing includes one at a
time to see if I can isolate the problem.
