ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: gnwiii@gmail.com
Subject: Re: Installation Problem
Date: Thu, 25 May 2006 13:52:11 -0300	[thread overview]
Message-ID: <22af238a0605250952y9a994fbnab1b342cfed31f06@mail.gmail.com> (raw)
In-Reply-To: <7.0.1.0.0.20060525083953.01d2c648@3dsafety.com>

On 5/25/06, Neal Lester <neal@3dsafety.com> wrote:

> I renamed my input file to temp.tex.
>
> Now I get:
>
> kpathsea: Running mktexfmt cont-en.fmt
> mktexfmt: No such file or directory
> I can't find the format file `cont-en.fmt'
>
> The file cont-en.fmt is in
>
> texmf-linux/web2c/pdfetex
>
> I added the following line to texmf/context/config/texexec.ini
>
> TeXFormatPath     texmf-linux/web2c/pdfetex     fmt files

When you run ". setuptex <your_texroot_path>" you should end up with

TEXFORMATS='$TEXMFOS/web2c/{$engine,}'

If this is OK, then try "texexec --check" and "texexec --verbose test"
to see if you get some hints.

> That didn't help, so I copied texexec.ini to
>
> texmf-linux/bin
>
> but that didn't help either.

The kpsewhich utility is used to search the ls-R databases and can
also display the values of variables.  Unfortunately, the documentation
is probably not in the minimal configuration you have.  If you can
find another system with TeX, try "info kpsewhich".

-- 
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia

  reply	other threads:[~2006-05-25 16:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 14:48 Neal Lester
2006-05-25 15:15 ` Taco Hoekwater
2006-05-25 15:48   ` Neal Lester
2006-05-25 16:52     ` gnwiii [this message]
     [not found]       ` <22af238a0605250952y9a994fbnab1b342cfed31f06@mail.gmail.com >
2006-05-25 18:39         ` Neal Lester
2006-05-26 10:50           ` gnwiii
2006-05-25 18:41   ` Neal Lester
2006-05-25 16:51 ` gnwiii
2006-05-25 16:58   ` gnwiii
  -- strict thread matches above, loose matches on Subject: below --
2006-05-23 23:51 Neal Lester
2006-05-24  7:49 ` Taco Hoekwater
2006-05-24 13:45   ` Neal Lester
2006-05-24 16:07     ` gnwiii
     [not found]       ` <22af238a0605240907w2cf73504h3299e1bf6392de2c@mail.gmail.co m>
2006-05-24 21:36         ` Neal Lester
2006-05-25 12:20           ` gnwiii
2006-05-24  8:13 ` Hans Hagen
2006-05-03 11:31 installation problem Karsten Heymann
2006-05-05  7:49 ` Taco Hoekwater
2006-05-05  8:02   ` Karsten Heymann
2006-05-05 10:49 ` Hans Hagen
2006-04-08  2:12 Installation problem Pavel Stupin
2006-04-08  3:11 ` Mojca Miklavec
2006-04-08 11:50 ` Hans Hagen
2004-10-16  5:43 Installation Problem David Arnold
2004-10-16  9:55 ` Patrick Gundlach
2004-10-16 15:46 ` Problem Larry Stamm
2004-10-17 20:09   ` Installation Problem h h extern
2004-10-17 20:21 ` h h extern
2004-06-21  8:28 Installation problem Matt Gushee
2004-06-21  8:45 ` Patrick Gundlach
2004-06-21  9:22   ` Matt Gushee
2004-06-21  9:29     ` Patrick Gundlach
2004-06-21 10:06       ` Matt Gushee
2004-06-21 14:57         ` Patrick Gundlach
2004-06-21 15:11           ` Hans Hagen
2004-06-21 20:51             ` Patrick Gundlach
2004-06-22  8:32               ` Hans Hagen
2004-06-22  8:51                 ` Patrick Gundlach
2004-06-22 10:21             ` Patrick Gundlach
2004-06-25  8:32     ` Patrick Gundlach
2004-06-21  8:46 ` Thomas A. Schmitz
2004-06-21  9:05   ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22af238a0605250952y9a994fbnab1b342cfed31f06@mail.gmail.com \
    --to=gnwiii@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).