Re: Problem with kpsewhich on a new instal

I do need to use a PATH relative to my home directory because the admin's
on the machine move users home directories frequently... and in fact, most
things are broken:

$ which lualatex
~/usr/local/texlive/2026/bin/x86_64-linux/lualatex

$ lualatex test
lstat(./lualatex) failed: ./lualatex: No such file or directory
kpathsea: Can't get directory of program name: ./lualatex

PN

On Sun, May 17, 2026 at 5:51 PM Paulo Ney de Souza <[email protected]>
wrote:

> I just finished an install on a shared hosting machine, and some things
> are working properly, but not "kpsewhich".
>
> When I run:
>
> $ which kpsewhich
>
> ~/usr/local/texlive/2026/bin/x86_64-linux/kpsewhich
>
> which is the correct answer. But when I run the command:
>
> $ kpsewhich --var-value TEXMFLOCAL
>
> lstat(./kpsewhich) failed: ./kpsewhich: No such file or directory
> kpathsea: Can't get directory of program name: ./kpsewhich
>
> which is a very weird result.
>
> Running the full path, I get the correct answer:
>
> $ ~/usr/local/texlive/2026/bin/x86_64-linux/kpsewhich --var-value
> TEXMFLOCAL
>
> /home/1/p/pa/pauloney/usr/local/texlive/texmf-local
>
> I thought I had seen this some 20 years ago ... is this something that
> will be fixed?
>
>
> Paulo Ney
>