ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Jan Mikkelsen via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: the system not working on Linux 32 with Context-lmtx
Date: Thu, 21 Jul 2022 21:28:08 +0200	[thread overview]
Message-ID: <92267b62-7b23-fb94-11bc-cad11e9a3b26@freedom.nl> (raw)
In-Reply-To: <749020B0-15B0-41B3-9CCC-031A231BB2DE@transactionware.com>

On 7/20/2022 3:31 PM, Jan Mikkelsen via ntg-context wrote:
> Hi,
> 
> I had/have a very similar problem on FreeBSD with TeXLive 2021, with the same context.lua not found message, which I posted about a while ago.
> 
> I “resolved” it by setting TEXMF to point to my texmf-dist directory, in my case /usr/local/share/texmf-dist. It would be nice for it to work without setting TEXMF.
> 
> Without setting TEXMF, running "mtxrun —generate” guesses a little differently, then attempts to scan all of /usr, and then fails when parts have no read permission.
> 
> I suspect it is working when you are in /usr/share/texmf-dist because the “collapsepath” function in mtxrun is collapsing “/../..” from /usr/bin to “.” instead of “/“. (Which seems like a bug, but I’m not sure.)
> 
> If I run “TEXMF=/usr/local/share/texmf-dist context file.tex” things run correctly, and a ~/.texlive2021 directory is created. Running “TEXMF=/usr/local/shared/texmf-dist mtxrun —generate” runs without error but also doesn’t generate a ~/.texlive2021 directory.
> 
> The real problem seems to be that mtxrun doesn’t deal well with the filesystem layout case of “/top-level/bin/mtxrun” and “/top-level/share/texmf-dist”.
you should not run/mix lmtx with texlive

- we use luametatex as runner for both luametatex and luatex runs
- mtxrun.lua and context.lua are both in the bin path (as usual)
- mtxrun.exe and context.exe are symlinks to luametatex.exe

that is the same for all platforms but in tex live on windows there is 
some small stub (i'm bot even sure what nowadays) that starts luatex in 
texlue mode  and then loads mtrun.lua; on unix it is supposed to shebang 
(therefore there mxrun.lua is just mtxrun).

no shebanging in lmtx: as said, just a symlink to the bin that then 
picks up mtxrun.lua : all operating systmes treated equal.

So, mixing these approaches in unlikelty to work unless one makes sure 
that before installing lmtx first all traces of mtxrun and context in 
the bin paths are gone ... even then I'm not sure but others who mix 
might know.

(btw, why not keep lmtx separate from your texlive installation)

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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2022-07-21 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 17:10 Alain Delmotte via ntg-context
2022-06-27 18:00 ` Henning Hraban Ramm via ntg-context
2022-06-27 20:32   ` Pablo Rodriguez via ntg-context
2022-06-29  9:13     ` Alain Delmotte via ntg-context
2022-07-20 13:31       ` Jan Mikkelsen via ntg-context
2022-07-21 19:28         ` Hans Hagen via ntg-context [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=92267b62-7b23-fb94-11bc-cad11e9a3b26@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.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).