fixing kpathsea

[Lars Madsen]

what do you mean by root terminal

if you run that export line just as root, then that change does not affect your user only the root user in that terminal.

running that export command as just your own user should work, but it again only affects stuff you start from that terminal as you.

you make it permanent add the export tine to a profile file (I don't know if gentoo does things different than ubuntu), I tend to add it to both my .profile and .bashrc (just the latter is generally not enough as things started from a menu does not use spawn a bash shell), and the former is not enough if you also ssh into your box.


/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@math<http://au.dk/daleif@imf> / More information: http://au.dk/en/daleif@math<http://au.dk/en/daleif@imf>

________________________________
From: tex-live <tex-live-bounces+daleif=imf.au.dk at tug.org> on behalf of N. Andrew Walsh <n.andrew.walsh at gmail.com>
Sent: 13 November 2019 16:39
To: Zdenek Wagner <zdenek.wagner at gmail.com>
Cc: tex-live <tex-live at tug.org>
Subject: Re: fixing kpathsea

Hi Zdenek,

On Wed, Nov 13, 2019 at 4:05 PM Zdenek Wagner <zdenek.wagner at gmail.com<mailto:zdenek.wagner at gmail.com>> wrote:

You must add the path to the binaries,

so, in a new (root) terminal, I entered the following command:

  export PATH=/[$HOME]/tex-local/texlive/2017/bin/x86_64-linux/:$PATH

(and also without the slash after .../x86_64-linux). Still the same error. That's where the TUG TL binaries reside. Do I need to use the path to my *system* texlive binaries?

Cheers,

A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/tex-live/attachments/20191114/15e41dcc/attachment-0001.html>