This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: kpathsea cannot read `texmf.cnf' under Cygwin 1.1.4
- To: "Dr. Volker Zell" <Dr dot Volker dot Zell at oracle dot com>
- Subject: Re: kpathsea cannot read `texmf.cnf' under Cygwin 1.1.4
- From: Jerome Benoit <JGMBenoit at Wanadoo dot fr>
- Date: Tue, 07 Nov 2000 19:12:23 +0100
- CC: Kevin_Wright at i2 dot com, cygwin at sourceware dot cygnus dot com
- References: <OF5C9B046B.48A52EC3-ON88256989.000290AE@i2.com> <kvhf5ju13v.fsf@vzell.de.oracle.com>
It is not a Cygwin problem:
in fact Cygwin is not DOSISH : that the point:
I plan to submit a change file sooner.
Jerome BENOIT
"Dr. Volker Zell" wrote:
>
> >>>>> "Kevin" == Kevin Wright <Kevin_Wright@i2.com> writes:
>
> Kevin> Jerome,
> Kevin> I found some of my notes from building teTeX which uses some of the same
> Kevin> utilities. Here's what I found:
>
> Kevin> /usr/local/bin/mktexlsr:
> Kevin> if test -z "$COMSPEC" && test -z "$ComSpec"; then SEP=':'; else SEP=';';
> Kevin> fi
>
> Kevin> changed this to SEP=':'
>
> Hi
>
> I compiled teTex-1.0 under cygwin-1.1.5-4 and changed SEP to : as recommended above.
> Compiling tex files and previewing with xdvi works like a charm.
> The only problem is that the automatic font generation facility of tetex always places
> the resulting .pk files in the directory where the dvi file is found.
>
> It doesn't matter how I setup the font directory.
>
> I checked the tetex config files against my linux and solaris configuration, and couldn't find
> any differences. So maybe it's a cygwin problem.
>
> Is anybody out there who's using tetex with cygwin and seeing the same problem, or better
> has an answer ?
>
> Ciao
> Volker
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com