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/
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.
I ran into a similar problem in the past because the installation script install.sh says the following, among other things: "If you want to run ConTeXt everywhere, you need to adapt the path, like: [lmtx path]/bin:[lmtx path]/tex/texmf-linux-64/bin:[the rest of my path]" Doing as suggested, when mtxrun is launched the first binary is used because [lmtx path]/bin comes first in the PATH. My question is then how do you usually run mtxrun: 1) always writing the full path of the correct executable, 2) avoid putting [lmtx path]/bin in PATH, 3) putting [lmtx path]/bin _after_ [lmtx path]/tex/texmf-linux-64/bin in the PATH I'm asking here because option 1 is correct but not very handy, while 2) and 3) are different from what the installer says and they seemed to give other problems when I tried them. Thank you in advance, LD
On Fri, 14 Feb 2020, Luca Donetti wrote:
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/
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.
I ran into a similar problem in the past because the installation script install.sh says the following, among other things: "If you want to run ConTeXt everywhere, you need to adapt the path, like:
[lmtx path]/bin:[lmtx path]/tex/texmf-linux-64/bin:[the rest of my path]"
Doing as suggested, when mtxrun is launched the first binary is used because [lmtx path]/bin comes first in the PATH. My question is then how do you usually run mtxrun: 1) always writing the full path of the correct executable, 2) avoid putting [lmtx path]/bin in PATH, 3) putting [lmtx path]/bin _after_ [lmtx path]/tex/texmf-linux-64/bin in the PATH
I'm asking here because option 1 is correct but not very handy, while 2) and 3) are different from what the installer says and they seemed to give other problems when I tried them.
I always follow 2. I don't think that [lmtx path]/bin should ever be in the PATH except when updating the installation. Aditya
On Fri, Feb 14, 2020 at 08:59:57PM +0100, Luca Donetti wrote:
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/
Hi Luca,
1) always writing the full path of the correct executable,
I don't know which operating system you're using. On linux instead of writing the full path I'm using the command "alias" in my ".bashrc" file. So, Adityas proposal on mtxrun (Date: Wed, 12 Feb 2020 00:24:21 -0500 (EST)) becomes: alias context='~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --autogenerate --script context' with 'context-lmtx' being the directory, where I installed context. With this you invoke your context file with "context your-file.tex" I cancelled all context stuff in my PATH variable. Don't forget to 'source ~/.bashrc' afterwards.
2) avoid putting [lmtx path]/bin in PATH,
Yes, this could be a solution too, in my opinion.
3) putting [lmtx path]/bin _after_ [lmtx path]/tex/texmf-linux-64/bin in the PATH
I'm asking here because option 1 is correct but not very handy, while 2) and 3) are different from what the installer says and they seemed to give other problems when I tried them.
I hope this helps you! At least in the case you're using linux. Best wishes, Rudolf
On 15-02-2020 06:40, Rudolf Bahr wrote:
I hope this helps you! At least in the case you're using linux.
it appears as that many of the files in the two path are sort of identical: ~/data/context $ md5sum bin/mtxrun tex/texmf-linux-64/bin/luametatex b95ca64fabcb3f09edd861c4b87671cc bin/mtxrun b95ca64fabcb3f09edd861c4b87671cc tex/texmf-linux-64/bin/luametatex $ md5sum bin/mtxrun.lua tex/texmf-linux-64/bin/mtxrun.lua 4d73c3608cc2463e80c59942b3db7158 bin/mtxrun.lua 4d73c3608cc2463e80c59942b3db7158 tex/texmf-linux-64/bin/mtxrun.lua There is probably a reason for it ;-) .F
On Sat, 15 Feb 2020, Floris van Manen wrote:
On 15-02-2020 06:40, Rudolf Bahr wrote:
I hope this helps you! At least in the case you're using linux.
it appears as that many of the files in the two path are sort of identical:
~/data/context
$ md5sum bin/mtxrun tex/texmf-linux-64/bin/luametatex b95ca64fabcb3f09edd861c4b87671cc bin/mtxrun b95ca64fabcb3f09edd861c4b87671cc tex/texmf-linux-64/bin/luametatex
$ md5sum bin/mtxrun.lua tex/texmf-linux-64/bin/mtxrun.lua 4d73c3608cc2463e80c59942b3db7158 bin/mtxrun.lua 4d73c3608cc2463e80c59942b3db7158 tex/texmf-linux-64/bin/mtxrun.lua
There is probably a reason for it ;-)
But mtxrun looks for location of texmfcnf file based on its location, so which file is invoked makes a difference. Aditya
participants (4)
-
Aditya Mahajan -
Floris van Manen -
Luca Donetti -
Rudolf Bahr