Am 13.04.2015 um 14:19 schrieb Masamichi HOSODA:
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.
I have just installed lilypond-2.19.18-1.linux-x86.sh on another machine
running Debian 7 stable with latest updates. And the error is identical.
Maybe (this is a big maybe) I'll have a chance to test it on another
(different) 32bit Linux installation later today, but that's not sure at
all.
What kind of dependencies could I look for that could be handled by GUB
or documented as requirements?
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
