On Tuesday, 25 July 2000, Carsten Block writes:
> Please check all of your TeX related environment variables. I think they
> should end with a ':'. I can reproduce this behaviour by setting TEXTFM="." b
+ ut
> it works ok with TEXTFM=".:". I think this is already mentioned in
> INSTALL.txt, lines 113-116:
Hmm, I don't have any:
12:56:29 appel ~/usr/src/lilypond$ env | grep -i tex
TEXINPUTS=.::/home/fred/tex/sty:/home/fred/usr/src/lilypond/ps:/home/fred/usr/src/lilypond/tex:/home/fred/usr/src/lilypond/mf/out
Here's what I tried for textfm:
export TEXTFM=/usr/share/texmf/fonts/tfm:.:
12:58:14 appel ~/usr/src/lilypond$ export TEXTFM=/usr/share/texmf/fonts/tfm:.:
12:58:15 appel ~/usr/src/lilypond$ lilypond input/trip.ly
GNU LilyPond 1.3.74.jcn3
...
kpathsea: Running mktextfm cmr10
Arg.
> | The empty path component represents TeX and MetaFont's default
> | search paths. Scripts with the proper paths for the bourne and C-shell
> | respectively are generated in `buildscripts/out/lilypond-profile' and
> | `buildscripts/out/lilypond-login' during compilation.
OK, but I've done some checking using KPATHSEA_DEBUG=-1, and it turns out
that kpsewhich and mktextfm read /usr/share/texmf/web2c/texmf.cnf, but
the kpathsea lib does not -> so no default paths. If I set
export TEXMFCNF=/usr/share/texmf/web2c
the kpathsea lib does read the texmf.cnf file, but still can't find
any tfms. I know where the tfm file is, kpsewhich knows it, but I
can't seem to tell kpathsea where to look; TEXFONTS, TEXTFM, TEXMF,
TFMFONTS, VARTEXFONTS? I'm using tetex on a pcc (tetex-0.9-17.src.rpm),
all 1.x versions I tried crash on ppc.
> We should add an option --enable-kpathsea to the configure script. If it
That's what I've done for pl75. It seems the only way to go for GNU/Windows,
currently, and certainly until I can get kpathsea to function correcly
on my ppc linux box. Am I the only one who has troubles with kpathsea?
> BTW, there is fpTeX, a "teTeX for Windows", which probably uses the
> kpathsea lib on windows systems. Does someone on the list use it and
> knows more?
Well, that's exactly the problem, I guess. There's a plethoria of
TeX distributions for Windows. We probably cannot cater for them
all (targeting a specefic one is not even possible, currently) with
one kpathsea binary lib?
Greetings,
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
