> This is on Debian with the linux-386 binary and applies to _any_ file,
> even
> { c }
> .
>
> Compiling with the 2.19.17 binary works.
> Compiling with the 2.19.18 binary fails.
> Compiling with a custom build from current master works.
>
> As there are no relevant commits between the 2.19.18 tag and current
> master I assume this is due to the binary build (i.e. recent GUB
> changes).
I've tested official binary lilypond-2.19.18-1.linux-x86.sh
on both Ubuntu 32 bit and Ubuntu 64 bit.
It is fine for my both environments.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
