Re: file fmutil

What an interesting way of putting things.

Here is a copy of my current path from echo $PATH:
/usr/local/texlive/2025/bin/x86_64-linux:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

The one (below) about which you complain comes from this insertion into 
fmutil:

+  warn "PATH=$ENV{PATH}\n";

So this means fmutil is getting an incorrect value.

However if I run from the command line, all is well. There are only 
references to texlive.

Greg

On 2025-11-26 18:46, David Carlisle wrote:
>
> > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:
>
> so as stated originally your PATH is wrong: you have the standard bin 
> directories in front of the texlive 2025, so you are using the debian 
> system texlive not texlive 2025 from tug.
>
> but you are getting the texlive mktexfmt presumably you do not have a 
> copy of that with the system tex.
>
>
> On Wed, 26 Nov 2025 at 23:41, Greg Bennett <[email protected]> wrote:
>
>     Karl, yes I am.
>
>     Running a test file from the command line all references are to
>     /usr/local/texlive/2025/and friends
>
>     Here's what I get in TeXstudio's Messages tab after using it on
>     the same test file:
>
>     Process started: pdflatex -synctex=1 -interaction=nonstopmode
>     "gtest".tex
>
>     kpathsea: Running mktexfmt pdflatex.fmt
>
>     PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/texlive/2025/bin/x86_64-linux
>     Use of uninitialized value $TEXFMROOT in concatenation (.) or
>     string at /usr/local/texlive/2025/bin/x86_64-linux/mktexfmt line
>     19. got: /usr/local/texlive/2025/bin/x86_64-linux/mktexfmt:
>     kpsewhich -var-value=TEXMFROOT failed, aborting early. BEGIN
>     failed--compilation aborted at
>     /usr/local/texlive/2025/bin/x86_64-linux/mktexfmt line 27.
>
>     Process exited with error(s)
>
>
>     It seems that $TEXFMROOT is standing in the way.
>
>     I don't know why mktexfmt is being run either. The formats were
>     made by tl during installation.
>
>     Thanks for the help,
>     Greg
>
>     On 2025-11-26 17:18, Karl Berry wrote:
>>     Greg, I wonder if PATH that fmtutil is running with is somehow not the
>>     same PATH as you are running from the command line.
>>
>>     Are you still trying to get this to work under TeXstudio (or another
>>     frontend), or does the error happen on the command line? If it's only
>>     TeXstudio, I would guess you need to configure the frontend, somehow.
>>     (I've never used them, so don't know specifics.)
>>
>>     There's also a question of why mktexfmt is being run at all, since
>>     installation normally creates all the .fmt files (unless you explicitly
>>     disabled that). Which also, together with your question about
>>     /usr/share, sounds like the frontend is not finding your TL25
>>     installation, and is instead using what's on the system
>>     (/usr/bin/... instead of /usr/local/texlive/2025/...).
>>
>>     Finally, can you try adding these two debugging lines to yourfmtutil.pl <http://fmtutil.pl>
>>     and show us what the output is? (I rather suspect a differentfmtutil.pl <http://fmtutil.pl>
>>     is being called and you won't see this output.)
>>
>>     ---fmtutil.pl <http://fmtutil.pl>	(revision 76944)
>>     +++fmtutil.pl <http://fmtutil.pl>	(working copy)
>>     @@ -17,2 +17,4 @@ BEGIN {
>>         $TEXMFROOT = `kpsewhich -var-value=TEXMFROOT`;
>>     +  warn "PATH=$ENV{PATH}\n";
>>     +  warn "got: $TEXMFROOT\n";
>>         if ($?) {
>