Did you run convert-ly from HEAD?
On Tue, Dec 31, 2024, 1:53 PM H. S. Teoh via LilyPond user discussion <
lilypond-user@gnu.org> wrote:
> Hi,
>
> I'm testing out the latest git HEAD version of lilypond with an
> orchestral score, and I'm getting this error:
>
> -------------
> Parsing...ERROR: In procedure %resolve-variable:
> Unbound variable: ly:duration-length
> ice-9/eval.scm:159:9: Throw to key `numerical-overflow' with args
> `("divide" "Numerical overflow" #f #f)'.
> -------------
>
> There's no indication of what in the score might have triggered this
> error. Previous versions of lilypond compile the score just fine, so
> I'm at a loss as to what the problem might be. The last good version
> AFAIK is commit f1ad21caa. The following commit, 6c1081a82, appears to
> be the change that broke this, though I've no idea why it should, and
> what my score has to do with it (nowhere in my score do I reference
> ly:duration-length directly).
>
> I'd reduce the score to narrow down the problem, but since it's rather
> large and contains auto-generated parts, reduction is very
> time-consuming unless anyone has any ideas on where the problem might be
> so that I can narrow it down quicker.
>
>
> T
>
> --
> What do you call a boomerang that doesn't come back? A stick.
>
>
