On Fri, 25, Apr, 2003 at 12:42:31PM +0200, Mats Bengtsson spoke thus..
Sorry, I didn't read every line of your log.
There's no need to install the fonts in /usr/share/texmf/,
that's why we set the TEXMF variable in lilypond-profile.
On the other hand, it shouldn't hurt until the moment you
utdate Lilypond and forget to update the fonts.
I'll try and remember :-) Actually, having just tried the commands
below, it looks like it's seeing them in /usr/share/lilypond anyways
What do the following commands return?
kpsewhich feta20.mf
kpsewhich feta20.afm
kpsewhich feta20.pk
address@hidden:~]$ source src/lilypond-1.6.9/buildscripts/out/lilypond-profile
address@hidden:~]$ kpsewhich feta20.afm
/usr/share/lilypond/1.6.9/fonts/afm/feta20.afm
address@hidden:~]$ kpsewhich feta20.pk
address@hidden:~]$ kpsewhich feta20.mf
/usr/share/lilypond/1.6.9/fonts/source/feta20.mf
So, the only one it can't see is the .pk file.
Did you, by the way, get any warning about a missing kpathsea library
during the configure?
Nope, and looking in the config.h file in the build tree shows:
/* define if you want KPATHSEA */
#define KPATHSEA 1
/* define if you have kpatsea header */
#define HAVE_KPATHSEA_KPATHSEA_H 1
/* define if you have kpse_find_file */
#define HAVE_KPSE_FIND_FILE 1
/* define if you have kpse_find_tfm */
#define HAVE_KPSE_FIND_TFM 0
Thanks,
Mark