2008/3/8, John Mandereau <[EMAIL PROTECTED]>:
> This certainly happens because you've removed settings files and
> directories (~/.*); create a new user with your distro's administration
> tools, and copy ~/.* directories from this new user's home into your
> home directory.
This finally worke
Le mercredi 05 mars 2008 à 17:48 +0100, Valentin Villenave a écrit :
> 2008/3/5, Mats Bengtsson <[EMAIL PROTECTED]>:
>
> > Have you tried simply undefining the GS_LIB environment variable
> > before you run LilyPond?
>
> Now I have :)
>
> The point is: now the conversion seems to work (at least
2008/3/5, Mats Bengtsson <[EMAIL PROTECTED]>:
> Have you tried simply undefining the GS_LIB environment variable
> before you run LilyPond?
Now I have :)
The point is: now the conversion seems to work (at least no error
message is printed); however the pdf I'm getting now are not readable
at al
Valentin Villenave wrote:
I hope you have checked that you don't have any suspicious environment
variable settings.
Hmm... I don't really know how to check that. I just checked that
$GS_LIB is indeed my ~/.fonts directory, and I tried to have a look in
/etc/profile.d/ to check if the
2008/3/5, Mats Bengtsson <[EMAIL PROTECTED]>:
> 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
Yes, I noticed that after posting it.
> When comparing to the printouts I
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 th
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.
L
Since the error messages appear after the call to gs, I would still
suspect that ghostscript is the culprit, especially if you don't get any
PDF file.
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
Hi everybody,
I recently tried to merge Rune's branch into my local master branch,
and it went surprinsingly fine (just a couple of minor conflicts, in
convertrules.py and in VERSION). After having fixed the conflicts, I
could launch a make and a make install.
*But*
Ever since then, everytime I
