ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: latest beta and file mismatch problem
Date: Wed, 2 Dec 2009 12:55:07 +0100	[thread overview]
Message-ID: <6faad9f00912020355t17d4a016r27ebce8c794126a@mail.gmail.com> (raw)
In-Reply-To: <83158BB8-93FD-4991-BB54-B2DA63B62C2A@Princeton.edu>

On Wed, Dec 2, 2009 at 12:49, Bowen Alan C. wrote:
> Thanks, Mojca.
> With .bash_profile now reading .
> /Applications/ConTeXtMinimals/tex/setuptex, I ran texexec --make --all
> successfully. But I still could not process a .tex file: the error message
> was
> This is pdfTeX, Version 3.1415926-1.40.10 (Web2C 2009)
>  \write18 enabled.
>  (/Applications/ConTeXtMinimals/tex/texmf-context/web2c/natural.tcx)
> kpathsea: Running mktexfmt cont-en.fmt
> mktexfmt: No such file or directory
> I can't find the format file `cont-en.fmt'!
> TeXExec | runtime: 0.21928
> So I removed texmf-osx-intel from /ConTeXtMinimals/tex/. re-ran texexec
> --make --all. The error message is now
> texexec: Command not found.

Can you please send the output of:
> uname -m
> echo $HOSTTYPE
> sysctl -n hw.cpu64bit_capable
> echo $PATH
> ls /Applications/ConTeXtMinimals/tex/
> ls -l /Applications/ConTeXtMinimals/tex/texmf-osx-64/bin
> which pdftex
> which context
> which texexec
> kpsewhich context.tex

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-12-02 11:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 12:25 Bowen Alan C.
2009-12-01 15:40 ` Mojca Miklavec
2009-12-01 16:13   ` Bowen Alan C.
2009-12-02  8:13     ` Mojca Miklavec
2009-12-02 11:49       ` Bowen Alan C.
2009-12-02 11:55         ` Mojca Miklavec [this message]
2009-12-02 12:07           ` Bowen Alan C.
2009-12-02 15:43             ` Mojca Miklavec
2009-12-02 16:36               ` Bowen Alan C.
2009-12-02 17:06                 ` Bowen Alan C.
2009-12-02 17:24                   ` Otared Kavian
2009-12-03 12:22                     ` Bowen Alan C.
2009-12-01 16:15   ` Bowen Alan C.
2009-12-01 16:17     ` Arthur Reutenauer
2009-12-01 16:21       ` Bowen Alan C.
2009-12-01 19:58     ` Bowen Alan C.
2009-12-01 20:26       ` Hans Hagen
2009-12-01 20:38         ` Otared Kavian
2009-12-01 21:09           ` Bowen Alan C.
2009-12-01 21:26             ` Otared Kavian
2009-12-01 21:41             ` Hans Hagen
2009-12-02  8:16             ` Mojca Miklavec
2009-12-02 11:59               ` Bowen Alan C.
2009-12-02 12:04                 ` Mojca Miklavec
2009-12-02 12:24                   ` Bowen Alan C.
2009-12-01 20:43         ` Bowen Alan C.
2009-12-01 20:28       ` Peter Münster
2009-12-01 21:10         ` Bowen Alan C.
2009-12-02 18:51 Bowen Alan C.

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=6faad9f00912020355t17d4a016r27ebce8c794126a@mail.gmail.com \
    --to=mojca.miklavec.lists@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).