> 1) configure complains that it cannot find guile-config.
> Cure: Install the libguile4-dev package.
>
> 2) Configure complains that guile should be newer than 1.3 even if
> libguile version is 1.3.15; this is just a warning but it is probably
> related to problem 3.
Yes, the warning is related to 3.
I think the problem is that `guile-config link` lists some
lib file that you don't have installed on your system.
Last time a similar problem was reported, I think it was
readline that was missing in the installation even though
guile-config claimed it needed it. Since Lilypond doesn't
use all of the Guile functions, libreadline wasn't needed,
except for the test that configure performs.
> 3) Link reports some undefined references:
> Cure:
> As suggested by Ian Stirling, after running configure, config.make has
> to be modified adding
> -lguile -lqthreads to the definition of EXTRA_LIBES.
That's what configure adds when it detects guile correctly.
> 4) dvips and xdvi are not able to find the feta*.mf files:
> Cure:
> Insert
> MFINPUTS=:/usr/local/share/lilypond/mf
> export MFINPUTS
> in .profile.
This will probably create tfm and pk file in every directory
where you use Lilypond. An alternative solution is to link
/usr/local/share/lilypond/mf into the standard teTeX tree.
For example, do
ln -s /usr/local/share/lilypond/mf /usr/lib/texmf/local/fonts/source/lilypond
(this can be different depending on your particular teTeX
installation.) Don't forget to run the command mktexlsr afterwards.
> 5) LaTeX is not able to find the feta*.tfm files.
> Cure: Not yet solved really, a workaround is to copy the files needed
> to the working directory.
See above.
/Mats
