ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rudolf Bahr <quasi@quasi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mtxrun
Date: Wed, 12 Feb 2020 06:44:29 +0100	[thread overview]
Message-ID: <20200212054429.GB3784@nan> (raw)
In-Reply-To: <nycvar.YAK.7.77.849.2002111554020.919@ervasbepr.pvz.zptvyy.pn>

On Tue, Feb 11, 2020 at 03:57:27PM -0500, Aditya Mahajan wrote:
> On Tue, 11 Feb 2020, Rudolf Bahr wrote:
> 
> > 
> > On Tue, Feb 11, 2020 at 07:38:54PM +0100, Hans Hagen wrote:
> > > On 2/11/2020 6:26 PM, Rudolf Bahr wrote:
> > > 
> > > > "whereis mtxrun" gives:
> > > >     ~/context-lmtx/bin/mtxrun.lua
> > > >     ~/context-lmtx/bin/mtxrun
> > > >     ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua
> > > >     ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun
> > > i assume that you run the last one in this list, which is a copy of or link
> > > to the luametatex binary in the texmf-linux-64/bin path
> > 
> > 
> > Hans, thank you for your answer!
> > 
> > So I run explicitly the second one:
> >   ~/context-lmtx/bin/mtxrun --generate
> > but I got the same error.
> 
> This is the wrong binary. As Hans said (and also what I wrote in my message)
> is that you have to run the one in ~/context-lmtx/tex/texmf-linux-64/bin/
> 
> > Sorry, "~/context-lmtx/bin/mtxrun --generate" again resulted in:
> >   resolvers       | resolving | variable 'SELFAUTOLOC' set to 'bin'
> >   resolvers       | resolving | variable 'SELFAUTODIR' set to '.'
> >   resolvers       | resolving | variable 'SELFAUTOPARENT' set to '..'
> 
> I would suggest that you run these commands from outside the ~/context-lmtx
> directory, so that the above variables show the full path rather than the
> relative path.
> 
> > "mtxrun --generate" run outside the installation directory gets the same result:
> >   resolvers       | resolving | variable 'SELFAUTOLOC' set to '/home/sam/context-lmtx/bin'
> >   resolvers       | resolving | variable 'SELFAUTODIR' set to '/home/sam/context-lmtx'
> >   resolvers       | resolving | variable 'SELFAUTOPARENT' set to '/home/sam'
> >   resolvers       | resolving | variable 'TEXMFCNF' set to ''
> >   resolvers       | resolving | variable 'TEXMF' set to ''
> >   resolvers       | resolving | variable 'TEXOS' set to 'context-lmtx'
> 
> This shows that the wrong binary is being used. You are using the binary in
> /home/sam/context-lmtx/bin when you should use
> /home/sam/context-lmtx/tex/texmf-linux-64/bin.
> 
> Aditya


Thanks to Hans and Aditya!

Using the binaries in /context-lmtx/tex/texmf-linux-64/bin/ instead of
~/context-lmtx/bin/mtxrun brings the awaited result!

Remains the question why has it been possible to use the wrong binaries? How could
a context user know where the "good" binaries reside?
I put the PATH sequence of the official installation process as proposed into
my PATH variable and was using "mtxrun".

I shall eliminate the error causing context parts in my PATH variable. I'd suggest
to correct the proposed completion of PATH variable at the end of the installation
process. The knowledge about that has only been possible after a series of mails with
Pablo, Hans and Aditya.

Thanks again!

Rudolf
___________________________________________________________________________________
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-02-12  5:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 10:54 mtxrun Rudolf Bahr
2020-02-10 11:06 ` mtxrun Taco Hoekwater
2020-02-10 11:27   ` mtxrun Rudolf Bahr
2020-02-10 12:03 ` mtxrun Rudolf Bahr
2020-02-11 10:56   ` mtxrun Rudolf Bahr
2020-02-11 12:07     ` mtxrun Hans Hagen
2020-02-11 15:23       ` mtxrun Rudolf Bahr
2020-02-11 15:57         ` mtxrun Pablo Rodriguez
2020-02-11 17:26           ` mtxrun Rudolf Bahr
2020-02-11 18:38             ` mtxrun Hans Hagen
2020-02-11 20:41               ` mtxrun Rudolf Bahr
2020-02-11 20:57                 ` mtxrun Aditya Mahajan
2020-02-12  5:44                   ` Rudolf Bahr [this message]
2020-02-11 18:39             ` mtxrun Aditya Mahajan
2020-02-12  4:41               ` mtxrun Rudolf Bahr
2020-02-12  5:24                 ` mtxrun Aditya Mahajan
2020-02-12 10:05                   ` mtxrun Rudolf Bahr
     [not found] <mailman.0.1581764401.20240.ntg-context@ntg.nl>
2020-02-15 14:38 ` mtxrun Luca Donetti
2020-02-15 14:48 ` mtxrun Luca Donetti
     [not found] <mailman.474.1581455525.1332.ntg-context@ntg.nl>
2020-02-14 19:59 ` mtxrun Luca Donetti
2020-02-15  4:59   ` mtxrun Aditya Mahajan
2020-02-15  5:40   ` mtxrun Rudolf Bahr
2020-02-15 11:32     ` mtxrun Floris van Manen
2020-02-15 14:57       ` mtxrun Aditya Mahajan
  -- strict thread matches above, loose matches on Subject: below --
2011-01-23 16:21 MTXrun Herbert Voss
2011-01-23 17:43 ` MTXrun Vedran Miletić
2011-01-23 19:25   ` MTXrun Hans Hagen
2008-06-17 16:49 mtxrun Hans van der Meer
2008-06-17 17:29 ` mtxrun Hans Hagen
2008-06-17 17:34 ` mtxrun Taco Hoekwater
2008-06-17 19:47 ` mtxrun Aditya Mahajan
2008-06-18  8:12   ` mtxrun Hans van der Meer
2008-06-18  9:37     ` mtxrun Hans Hagen
2008-06-18 11:54     ` mtxrun Taco Hoekwater

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=20200212054429.GB3784@nan \
    --to=quasi@quasi.de \
    --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).