ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans van der Meer <havdmeer@ziggo.nl>
Subject: Re: lmtx install fails to run
Date: Thu, 9 Jul 2020 17:39:38 +0200	[thread overview]
Message-ID: <e086033f-acf8-6d76-e4a8-7073524412d5@xs4all.nl> (raw)
In-Reply-To: <CDEEECC4-6D03-4213-B016-63E11C23E475@ziggo.nl>

On 7/9/2020 5:25 PM, Hans van der Meer wrote:
> After doing just now the standard: sh install.sh context will not run. 
> Why, because in the past it worked without a hitch.
> Now there is no format cont-en.
> 
> Did all sorts of the ususal things like remove the current cache, 
> context --make en, etc.
> 
> I guess the error is in the missing file. An overfsight somewhere?
> Below the last part of the context --make en run.
> Mark the lang-mis.mkxl is not found line.
> 
> met vriendelijke groet
> dr. Hans van der Meer
> 
> resolvers       > lua > loading file 
> '/Users/hansm/TeX/context-lmtx/tex/texmf-context/tex/context/base/mkiv/node-bck.lua' 
> succeeded
> close source    > level 1, order 83, name 'node-bck.mkiv'
> open source     > level 1, order 84, name 'pack-cut.mkiv'
> close source    > level 1, order 84, name 'pack-cut.mkiv'
> runtime error : input file 'lang-mis.mkxl' is not found, quitting
> resolvers       | formats |
> resolvers       | formats | binary path      : 
> /Users/hansm/TeX/context-lmtx/tex/texmf-osx-64/bin
> resolvers       | formats | format path      : 
> /Users/hansm/TeX/context-lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex
> resolvers       | formats | luatex engine    : luametatex
> resolvers       | formats | lua startup file : 
> /Users/hansm/TeX/context-lmtx/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua
> resolvers       | formats | context file     : 
> /Users/hansm/TeX/context-lmtx/tex/texmf-context/tex/context/base/mkiv/cont-en.mkxl
> resolvers       | formats | run time         : 0.499 seconds
> resolvers       | formats | return value     : error
> resolvers       | formats |
> system          | total runtime: 0.500 seconds of 0.604 seconds
hm, is that file on yoru system? what if you update again?

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2020-07-09 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 15:25 Hans van der Meer
2020-07-09 15:39 ` Hans Hagen [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=e086033f-acf8-6d76-e4a8-7073524412d5@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=havdmeer@ziggo.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).