ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Fatal format file error; I'm stymied
Date: Thu, 08 Nov 2001 18:57:12 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20011108185623.031459a8@server-1> (raw)
In-Reply-To: <Pine.LNX.4.21.0111081643310.7987-100000@x.opf.slu.cz>

At 04:46 PM 11/8/2001 +0100, you wrote:
> > At 03:15 PM 11/8/2001 +0100, Lukas Kubin wrote:
> > >i checked the web2c directory and it contains cont-en.efmt elatex.efmt
> > >etex.efmt pdfelatex.efmt and pdfetex.efmt files (among others, of
> > >course). I have no other .efmt files in the tetex tree.
> > >
> > >this what I've done before: I installed the tetex 1.0 binaries (yes it's
> > >old but I'm having problems compiling the new sources on tru64 unix). The
> > >ConTeXt in that version is quite old, so I downloaded and unzipped in the
> > >texmf tree the current beta. Then: texconfig confall, I turned cont-en on
> > >in the texconfig formats, texhash, texexec --make en. Then you suggested
> > >texexec --make --alone en nl , so I tried but no change when try texexec
> > >anyfile.tex
> >
> > did you also move the new texexec (>=2.4) to the right place?
>
>yes, I did.
>now I posted a new mail to the list. I wrote there now I
>started again with whole the installation. I deleted the tetex directory
>and installed it again. Then I tried to run the old context 1.9 and it
>resulted into the same error.
>thank you for your patience with me.

can you run texexec --verbose and check texexec,ini?

What happens if you leave the fmt files on the current path? Do you then 
also get an error?

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


       reply	other threads:[~2001-11-08 17:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5.1.0.14.1.20011108160724.03e9a9a0@server-1>
     [not found] ` <Pine.LNX.4.21.0111081643310.7987-100000@x.opf.slu.cz>
2001-11-08 17:57   ` Hans Hagen [this message]
2001-11-13 11:53     ` fixed - " Lukas Kubin
2007-11-02  2:38 Ernesto Schirmacher
2007-11-02  6:55 ` luigi scarso
2007-11-02  7:26 ` Taco Hoekwater
2007-11-02  8:17 ` Hans Hagen
2007-11-02 14:11   ` Aditya Mahajan
2007-11-05 12:40   ` Norbert Preining
  -- strict thread matches above, loose matches on Subject: below --
2001-11-08 15:41 Patrick Gundlach
2001-11-08 14:56 Patrick Gundlach
2001-11-08 15:09 ` Lukas Kubin
2001-11-08 17:58   ` Hans Hagen
2001-11-08 14:31 Patrick Gundlach
2001-11-08 14:48 ` Lukas Kubin
2001-11-08 14:15 Patrick Gundlach
2001-11-08 14:25 ` Lukas Kubin
2001-11-08 10:39 Patrick Gundlach
2001-11-08 14:01 ` Lukas Kubin
2001-11-07 18:35 Lukas Kubin
2001-11-08  8:48 ` Hans Hagen
2001-11-08  9:50   ` Lukas Kubin

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=5.1.0.14.1.20011108185623.031459a8@server-1 \
    --to=pragma@wxs.nl \
    --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).