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 21:47:03 -0400 [thread overview]
Message-ID: <20230411014703.rnl5sxgpi4ubitgv@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.
Of course I sourced it and complains about plain.tex
>
> > 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.
binaries.
Let's start over for the simple reason that texmfcnf.lua does not exist.
Not through a TeX Live infrastructure only installation anyway.
let's run ./install --modules=all and it rightly reports that
mtx-update | updating mtxrun for linux-64: rsync -tgo --chmod=a+x
'/home/ce/context-install/tex/texmf-context/scripts/context/lua/mtxrun.lua'
'/home/ce/context-install/tex/texmf-linux-64/bin/mtxrun'
mtx-update | run, rsync -tgo --chmod=a+x '/home/ce/context-install/tex/texmf-context/scripts/context/lua/mtxrun.lua'
'/home/ce/context-install/tex/texmf-linux-64/bin/mtxrun'
rsync: [Receiver] change_dir#3 "/home/ce/context-install/tex/texmf-linux-64/bin" failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(827) [Receiver=3.2.7]
resolvers | tds | no 'texmf-linux-64' under tree '/home/ce/context-install/tex'
Now. Let's add the directories, correct?
If you were to look at the following
resolvers | resolving | using configuration specification 'home:texmf/web2c;{selfautoloc:,selfautoloc:/share/texmf-local/web2c,selfautoloc:/share/texmf-dist/web2c,selfautoloc:/share/texmf/web2c,selfautoloc:/texmf-local/web2c,selfautoloc:/texmf-dist/web2c,selfautoloc:/texmf/web2c,selfautodir:,selfautodir:/share/texmf-local/web2c,selfautodir:/share/texmf-dist/web2c,selfautodir:/share/texmf/web2c,selfautodir:/texmf-local/web2c,selfautodir:/texmf-dist/web2c,selfautodir:/texmf/web2c,$SELFAUTOGRANDPARENT/texmf-local/web2c,selfautoparent:,selfautoparent:/share/texmf-local/web2c,selfautoparent:/share/texmf-dist/web2c,selfautoparent:/share/texmf/web2c,selfautoparent:/texmf-local/web2c,selfautoparent:/texmf-dist/web2c,selfautoparent:/texmf/web2c}'
resolvers | resolving |
resolvers | resolving | looking for regular 'texmfcnf.lua' on given path
'/home/ce/texmf/web2c' from specification 'home:texmf/web2c'
resolvers | resolving | looking for regular 'texmfcnf.lua' on weird path
'/home/ce/context-install/tex/texmf-linux-64/bin' from specification 'selfautoloc:'
you'd notice that is looking over and over for a texmfcnf.lua
But where is my texmfcnf.lua? Would you know? :) Because I don't. The
only instance of a texmfcnf.lua dates back to a prepackaged
installation that is no longer there anyway
it points to a prepackaged texlive which I'm not using and not planning
to.
and what I have under TEXMFHOME which doesn't amount to much anyway , or what's
important for the current issue is
amiga-pl.tcx cp8bit.tcx il2-t1.tcx mktex.opt tcvn-t5.tcx
cp1250cs.tcx empty.tcx kam-cs.tcx mktexdir texmf.cnf
cp1250pl.tcx fmtutil-hdr.cnf kam-t1.tcx mktexdir.opt updmap-hdr.cfg
cp1250t1.tcx fmtutil.cnf macce-pl.tcx mktexnam updmap.cfg
cp227.tcx il1-t1.tcx macce-t1.tcx mktexnam.opt viscii-t5.tcx
cp852-cs.tcx il2-cs.tcx maz-pl.tcx mktexupd
cp852-pl.tcx il2-pl.tcx mktex.cnf natural.tcx
which as you fully know, it doesn't help
What is TeX Live infrastructure doing is the question
It's besides the point to call out ./tlmgr install context here because
mtx is no longer there anyway
for what's worth
Welcome to TeX Live!
See ../texlive/2023/index.html for links to documentation.
The TeX Live web site (https://tug.org/texlive/) contains any updates and corrections. TeX Live is a joint project of the TeX user groups around the world; please consider supporting it by joining the group best for you. The list of groups is available on the web at https://tug.org/usergroups.html.
Add ../texlive/2023/texmf-dist/doc/man to MANPATH.
Add ../texlive/2023/texmf-dist/doc/info to INFOPATH.
Most importantly, add ../texlive/2023/bin/x86_64-linux
to your PATH for current and future sessions.
Logfile: ../texlive/2023/install-tl.log
>
> Aditya
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
[It is] best to confuse only one issue at a time.
-- K&R
___________________________________________________________________________________
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 1:47 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 [this message]
2023-04-11 2:36 ` Carlos via ntg-context
2023-04-11 3:54 ` Carlos via ntg-context
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=20230411014703.rnl5sxgpi4ubitgv@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).