Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> At the very least, the code in lily.scm should be fixed to set the
> running-from-gui? flag on a sensible basis. Failing that, the --safe
> switch should be honored by lily-parser-scheme.cc.
I misunderstood here the purpose of the --safe flag (th
Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
> But now there's a new, more subtle, one. Normal Debian automatic
> build procedure is to build things with input redirected from
> /dev/null.
Ok, I have found out (thanks to strace) where the rest of the output
is going; it lands in "generate-doc
So delightfully, mftrace version 1.1.17 does indeed fix the previous
build problems.
But now there's a new, more subtle, one. Normal Debian automatic
build procedure is to build things with input redirected from
/dev/null.
This causes a failure in running lilypond for documentation
generation.
Id like to update
my question. I now am getting this
error:
lilypond: /lib/libc.so.6: version `GLIBC_2.4' not found (required by /usr/lib/libpango-1.0.so.0)
This is the reason why want to use version 2.2.6, because I
don’t know what this message means or how to fix it. Thanks for
For all my questions regarding my problem, do I simply post
to lilypond-devel@gnu.org?
Anyway, I was told to install the stable version which is
posted at the homepage of lilypond. Every time I try to install
lilypond-2.6.4-1.i386.rpm (This is the stable version) I get these errors:
There's no need for a clean-fonts.sh anymore, since LilyPond
looks for the fonts in a version specific directory (see the printouts of
lilypond --verbose whateverfile.ly). I've never heard of such problems,
my only guess is that it's related to the font producing commands that
you used when compil
