Valentin Villenave wrote:
2008/3/5, Mats Bengtsson <[EMAIL PROTECTED]>:
When you try running the GUB binary release, check the outputs of
lilypond --verbose ...
to see if it in any way uses any file that's also read by your home-compiled
version. You might also want to try to remove the cached font database.
LOL -- did I mention that, in addition to the insane rm-rf /usr/local*
I did, I also did a quite brutal rm-rf ~/.*
(Yes, I'm just that crazy :)
Anyway, I ran LilyPond in verbose mode (full output follows)
Indeed, it keeps calling a weird ghostscript directory in
/usr/bin/../share that doesn't exist (since Lily is in /usr/local by
default.
Weird.
If you read the full line of the printout, you will notice that it
indeed searches
in the relevant place:
/usr/local/lilypond/usr/bin/../share/ghostscript/8.57/lib
When comparing to the printouts I get when running a GUB installation,
it seems very similar and it is for example normal that it doesn't find any
setting for GS_FONTPATH. However, I notice that it also adds
/home/valentin/.fonts to GS_LIB, which I cannot repeat here unless
I have the environment variable GS_LIB set when calling LilyPond.
I hope you have checked that you don't have any suspicious environment
variable settings.
/Mats
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
