From: Carlos via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Carlos <linguafalsa@gmail.com>
Subject: Re: /usr/bin/env texlua no such file or directory; ~/context/tex is not a valid TEXROOT path; no file plain.tex
Date: Mon, 10 Apr 2023 23:54:17 -0400 [thread overview]
Message-ID: <20230411035417.iptb7iutuwcek5iq@gmail.com> (raw)
In-Reply-To: <s1sp4o58-o927-872p-n469-254qr089n22q@hzvpu.rqh>
On Mon, Apr 10, 2023 at 08:51:58PM -0400, Aditya Mahajan via ntg-context wrote:
> On Mon, 10 Apr 2023, Carlos via ntg-context wrote:
>
> > I'm just following some of the standalone installation instructions
> > as per the wiki alongside a TeX Live installation, but there are a
> > few things that don't add up or I can't seem to add them up :).
> >
> > first, while I was trying to mtxrun --generate it returned
> >
> > /usr/bin/env texlua no such file or directory
> >
> > So I thought heck, perhaps by creating a symbolic link we'll call it
> > a day, but that wasn't enough, nope.
> >
> > This is is circa 21st century ladies and gentlemen!
> >
> > so I thought, alright, since there seems ot be a a problem with texlua,
> > let's also add it to path somehow.
>
> Did you source the `setuptex` script, which sets the correct path.
>
> > So with that out of the way, we'll move on to the next step and change
> > to a directory and try to call out mtxrun --generate again
> >
> > It returns:
> >
> > mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC'
> > set to '/home/ce/context/bin' resolvers | resolving | variable
>
> This appears to be the wrong mtxrun binary. You should include the PATH variable listed as part of the installation. It should point to `/home/ce/context/texmf-linux-64/bin` or something similar.
with texmfcnf.lua and the contextbinary from just hte TeX Live infrastructure
there is an interesting conflict with the same ol' same ol'
anyhow
[2/2, 00:02/02:56] install: context [92021k]
running mktexlsr ...
done running mktexlsr.
running mtxrun --generate ...
done running mtxrun --generate.
running context --luatex --generate ...
done running context --luatex --generate.
running updmap-sys ...
done running updmap-sys.
then
context <file>
mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
context --luatex --generate
mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
same as with
context --generate
mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
so it's an either or. texmfcnf.lua in place mtxrun would definitely
go through but breaks context calls, while without it, a context call
is just ostracized to a
context --generate --luatex
mtx-context | redirect luametatex -> luatex: luatex --luaonly "/opt/texlive/2023/bin/x86_64-linux/mtxrun.lua" --generate --redirected
but that's not what I had in mind.
mtxrun --script cache --erase
mtxrun | unknown script 'cache.lua' or 'mtx-cache.lua'
--
Real Programmers think better when playing Adventure or Rogue.
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-04-11 3:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 23:58 Carlos via ntg-context
2023-04-11 0:51 ` Aditya Mahajan via ntg-context
2023-04-11 1:47 ` Carlos via ntg-context
2023-04-11 2:36 ` Carlos via ntg-context
2023-04-11 3:54 ` Carlos via ntg-context [this message]
2023-04-11 4:01 ` Alan Braslau via ntg-context
2023-04-11 9:11 ` Carlos via ntg-context
2023-04-11 9:23 ` Hans Hagen via ntg-context
2023-04-11 10:00 ` Carlos via ntg-context
2023-04-11 10:20 ` Hans Hagen via ntg-context
2023-04-11 12:59 ` Carlos via ntg-context
2023-04-11 13:13 ` Carlos via ntg-context
2023-04-11 15:57 ` Hans Hagen via ntg-context
2023-04-12 2:32 ` Carlos via ntg-context
2023-04-11 5:01 ` Max Chernoff via ntg-context
2023-04-11 7:26 ` Hans Hagen via ntg-context
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=20230411035417.iptb7iutuwcek5iq@gmail.com \
--to=ntg-context@ntg.nl \
--cc=linguafalsa@gmail.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).