ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: timli2013@outlook.com
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: unknown script 'context.lua' or 'mtx-context.lua
Date: Sat, 1 Mar 2014 13:02:35 +0100	[thread overview]
Message-ID: <20140301130235.6935483f@iram-ha-003587.extra.cea.fr> (raw)
In-Reply-To: <COL127-W305D8535A80C83D5B442F4A9830@phx.gbl>

Hello,

This may be a sign of an incorrect PATH, picking-up TeXlive or
a system installed context. One solution is to *source* the tex/setuptex
script, another is to set your PATH with tex/texmf-ARCH/bin up front.

Alan




On Thu, 27 Feb 2014 11:08:35 +0000
Tim Li <timli2013@outlook.com> wrote:

> Hi guys,
> 
> I haven't played with ConTeXt for three month because of my
> examinations. Today, I delete the old version and reinstall a new one
> from the ConTeXt garden, but it seems that the new one can't run
> successfully. It says that unknown script 'context.lua' or
> 'mtx-context.lua. The error messages is the following:
> 
> mtxrun          | forcing cache reload
> resolvers       | resolving | looking for 'texmfcnf.lua' on given
> path '/home/peng/texmf/web2c' from specification 'home:texmf/web2c'
> resolvers       | resolving | looking for 'texmfcnf.lua' on weird
> path '/usr/bin/' from specification 'selfautoloc:' resolvers       |
> resolving | looking for 'texmfcnf.lua' on given path
> '/usr/bin/share/texmf-local/web2c' from specification
> 'selfautoloc:/share/texmf-local/web2c' resolvers       | resolving |
> looking for 'texmfcnf.lua' on given path '/usr/bin/share/texmf/web2c'
> from specification 'selfautoloc:/share/texmf/web2c' resolvers       |
> resolving | looking for 'texmfcnf.lua' on given path
> '/usr/bin/texmf-local/web2c' from specification
> 'selfautoloc:/texmf-local/web2c' resolvers       | resolving |
> looking for 'texmfcnf.lua' on given path '/usr/bin/texmf/web2c' from
> specification 'selfautoloc:/texmf/web2c' resolvers       | resolving
> | looking for 'texmfcnf.lua' on weird path '/usr/' from specification
> 'selfautodir:' resolvers       | resolving | looking for
> 'texmfcnf.lua' on given path '/usr/share/texmf-local/web2c' from
> specification 'selfautodir:/share/texmf-local/web2c' resolvers
> | resolving | looking for 'texmfcnf.lua' on given path
> '/usr/share/texmf/web2c' from specification
> 'selfautodir:/share/texmf/web2c' resolvers       | resolving |
> looking for 'texmfcnf.lua' on given path '/usr/texmf-local/web2c'
> from specification 'selfautodir:/texmf-local/web2c' resolvers       |
> resolving | looking for 'texmfcnf.lua' on given path
> '/usr/texmf/web2c' from specification 'selfautodir:/texmf/web2c'
> resolvers       | resolving | looking for 'texmfcnf.lua' on given
> path './../texmf-local/web2c' from specification
> 'selfautoparent:/../texmf-local/web2c' resolvers       | resolving |
> looking for 'texmfcnf.lua' on weird path './' from specification
> 'selfautoparent:' resolvers       | resolving | looking for
> 'texmfcnf.lua' on given path './share/texmf-local/web2c' from
> specification 'selfautoparent:/share/texmf-local/web2c'
> resolvers       | resolving | looking for 'texmfcnf.lua' on given
> path './share/texmf/web2c' from specification
> 'selfautoparent:/share/texmf/web2c' resolvers       | resolving |
> looking for 'texmfcnf.lua' on given path './texmf-local/web2c' from
> specification 'selfautoparent:/texmf-local/web2c' resolvers       |
> resolving | looking for 'texmfcnf.lua' on given path './texmf/web2c'
> from specification 'selfautoparent:/texmf/web2c' resolvers       |
> resolving | resolvers       | resolving | warning: no lua
> configuration files found resolvers       | resolving | no texmf
> paths are defined (using TEXMF) resolvers       | resolving |
> mtxrun          | the resolver databases are not present or outdated
> resolvers       | resolving | using suffix based filetype 'lua'
> resolvers       | resolving | remembering file 'mtx-context.lua'
> resolvers       | resolving | using suffix based filetype 'lua'
> resolvers       | resolving | remembering file 'mtx-contexts.lua'
> resolvers       | resolving | remembered file 'mtx-context.lua'
> resolvers       | resolving | using suffix based filetype 'lua'
> resolvers       | resolving | remembering file 'mtx-t-context.lua'
> resolvers       | resolving | using suffix based filetype 'lua'
> resolvers       | resolving | remembering file 'mtx-t-contexts.lua'
> resolvers       | resolving | remembered file 'mtx-t-context.lua'
> resolvers       | resolving | using suffix based filetype 'lua'
> resolvers       | resolving | remembering file 'context.lua'
> mtxrun          | unknown script 'context.lua' or 'mtx-context.lua'
> 
> Best wishes,
> Tim 		 	   		  

___________________________________________________________________________________
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:[~2014-03-01 12:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 11:08 Tim Li
2014-03-01 12:02 ` Alan BRASLAU [this message]

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=20140301130235.6935483f@iram-ha-003587.extra.cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    --cc=timli2013@outlook.com \
    /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).