Question

3

Bash refuses to execute correct binary

rated 0 times [ 3] [ 0] / answers: 1 / hits: 1312 / 1 Year ago, tue, march 14, 2023, 5:49:11

I've installed the current version of texlive (2012), which installs its binaries into /usr/local/texlive/2011/bin/i386-linux/. I subsequently added this directory to the PATH variable by modifying the /etc/environment file, since I want this installed for all users:

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/texlive/2012/bin/i386-linux"

I then proceeded to remove the texlive apt-suite packages, since I was getting errors when trying to compile .tex documents that showed me a texlive 2009 distribution came prepackaged with my Lubuntu 12.04.

Now something pretty strange happens:

~ which pdflatex

/usr/local/texlive/2012/bin/i386-linux/pdflatex

So it seems the binary is being found. Still, the following happens:

~ pdflatex foo.tex

/usr/bin/pdflatex: File not found!

Why is it looking ìn /usr/bin/? Is this some kind of bash internal cache for binary locations (I vaguely remember hearing something about this)?

What would be a possible fix?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

terose

Add To Favorites

Follow

Total Points: 185

Total Questions: 125

Total Answers: 131

Location: Venezuela

Member since Mon, Dec 13, 2021

2 Years ago

terose questions

1 VBoxClient: error while loading shared libraries: libXt.so.6:

Thu, Aug 26, 21, 05:47, 3 Years ago

1 How to turn off light on Logitech G502 mouse?

Sun, Jan 9, 22, 17:24, 2 Years ago

1 File permission numerical value of "rws"

Thu, Feb 10, 22, 17:13, 2 Years ago

1 How do I install and configure the latest version of `solaar` to manage my Logitech wireless mouse or keyboard on Linux Ubuntu?

Mon, Nov 7, 22, 03:34, 2 Years ago

1 No sound (After I removed Pulseaudio)

Sun, Jul 25, 21, 22:51, 3 Years ago

View All

answered 1 Year ago ardingiba · Accepted Answer

Very likely /usr/bin/pdflatex is a symbolic link to the package you just removed, which in turn doesn't exist. Try ls -l /usr/bin/pdflatex to see if it points to another file. If it's a broken symlink (the target doesn't exist) you can simply remove it and the next pdflatex in the PATH should be run.

which actually looks for the first executable in the PATH which exists. In other words, if you ln -s /non-existing/path /usr/local/sbin/pdflatex it will be ignored by which, even though /usr/local/sbin is first in the PATH.