"R. D. Davis" <[EMAIL PROTECTED]> writes:
> rhiannon[108]% ldd `which dvips`
> /usr/local/bin/dvips:
> libm.so.2 => /usr/lib/libm.so.2 (0x2808c000)
> libc.so.4 => /usr/lib/libc.so.4 (0x280a7000)
That suggests it does not use kpathsea. See Mats' message to try
kpathsea debugging i
One tricky aspect of dvips and the other programs that use the
kpathsea library is that the searched paths also depend on the
directory where the binary is installed. So, one thing to check
is if the programs kpsewhich and dvips are installed in the same
directory.
I hope that 'printenv TEXMF' retu
"R. D. Davis" <[EMAIL PROTECTED]> writes:
> Here are the results:
>
> rhiannon[101]% echo $TEXMF
> /usr/local/share/lilypond/2.0.1 /usr/local/share/texmf
> rhiannon[102]% kpsewhich music-drawing-routines.ps
> /usr/local/share/lilypond/2.0.1/tex/music-drawing-routines.ps
So with this setting kpath
"R. D. Davis" <[EMAIL PROTECTED]> writes:
> Opening pipe `kpsewhich feta20.pfa'
> Invoking `dvips -ta4 -Ppdf -G0 -u +lilypond.map -onewtest.ps newtest.dvi'This is
> dvips(k) 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com)
> ' TeX output 2003.11.16:2217' -> newtest.ps
> dvips: ! Cou
