Three related bugs...

[Jürgen Reuter]

Hi, I found three related bugs:

Bug #1:

ChangeLog says:

2006-06-19  Han-Wen Nienhuys  <address@hidden>
...
        * lily/main.cc: switch on relocation by default.


Unfortunately, this breaks lilypond-book on my machine.  I get the following
error:

ERROR: In procedure primitive-load-path:
ERROR: Unable to find file "lily.scm" in load path

Further investigation shows up the following reason:

warning: Relocation:
compile prefix=/home/reuter/project/lilypond-2.9/share/lilypond/2.9.10,
new prefix=/usr/local
PATH=/usr/local/bin (prepend)
...
Effective prefix: "/usr/local/bin/.."

(Note, that I have called autogen.sh with "--prefix=`pwd`".)
Since there is no lily.scm in /usr/local/..., lily dies.

Please note, that above error does not occur, if I invoke lilypond instead of
lilypond-book.

Bug #2:

I would be able to workaround Bug #1, if the lilypond command line option
"--relocate" (which, by the way, is not documented in the manual) could be used
to turn off relocation.  However, "--relocation" can only be used to turn on
relocation, but it is turned on by default, i.e. this command line option is
pointless.

Bug #3:

In order to investigate Bug #1, I called lilypond-book with option "-V".
Unfortunately, lilypond-book does not pass "-V" on to lilypond, such that "-V"
is of almost no value.

====

When using lilypond-book, I also have severe problems with finding the fonts on
my machine: ghostview barfs on the generated eps score line files (e.g.
lily-1234567890-1.eps) with "\invalidfont in findfont", while the complete file
(e.g. lily-1234567890.eps) is fine.  This behavior occurs also when invoking
lilypond directly (instead of lilypond-book).  I will eventually further
investigate.

Greetings,
Jürgen