SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
According to http://www.computerhope.com/unix/usetenv.htm, setenv is used in the C shell. If you're using the Bash shell, setting an environment variable is done with export. Can you post the info from the TeX docs and someone here should be able to tell you what needs to be done.
============================================================================
7) final configuration steps
============================================================================
Overview:
- set up PATH
- check environment
- configure teTeX using texconfig
- generate fonts with a batch job
- set up area for automatic font generation
Set up PATH:
===========
Set up your PATH to include the directory containing the just installed
binaries (e.g. /usr/local/teTeX/bin/i686-pc-linux-gnu); similarly, MANPATH
and INFOPATH to include the relevant newly installed subdirectories,
i.e. $prefix/man resp. $prefix/info. To avoid conflicts with a
possible different TeX installation, make sure to put the new directories
first. E.g. for setting PATH, use something like the following, but
replace i686-pc-linux-gnu by your actual platform directory:
PATH=/usr/local/teTeX/bin/i686-pc-linux-gnu:$PATH; export PATH
or
setenv PATH /usr/local/teTeX/bin/i686-pc-linux-gnu:$PATH
As an alternative to adjust PATH, you could as well create symbolic
links in a standard location such as /usr/local/bin:
Example using GNU-ls (which supports the "force" option):
ln -sf /usr/local/teTeX/bin/i686-pc-linux-gnu/* /usr/local/bin
Example using standard ln:
(cd /usr/local/teTeX/bin/i686-pc-linux-gnu; echo *) \
| (cd /usr/local/bin; xargs rm -f)
ln -s /usr/local/teTeX/bin/i686-pc-linux-gnu/* /usr/local/bin
This is the segment of the doc of TeTeX that I dont understand...
Well, theres a problem : when I do the PATH=, it works in the terminal ONLY IF I DONT CLOSE IT!!!, but if I open back rxvt, the PATH= is not in set...
And the MANPATH= is the same thing...
I would like rxvt to ALWAYS know where is the MAN pages of TeX...
I assume you're using Bash as your shell... If so, do you want the change made just for yourself? Add the following to the file .bash_profile in your home directory. You'll have to do the same for MANPATH and INFOPATH:
If this is for all users, check that there is a section in /etc/profile that says:
Code:
for profile_script in /etc/profile.d/*.sh ; do
if [ -x $profile_script ]; then
. $profile_script
fi
done
If there is, you can create a file called /etc/profile.d/tex.sh and add the same lines to it instead (from memory, the file needs to be executable). If the profile.d stuff is not there, add the lines to /etc/profile. Either way, the next time you login those variables should already be set for you.
Running the following will list all of the links in /usr/local/bin. If you don't get any false positives (ie, files you don't want to delete) then you can change the ls -l to rm -f:
Code:
find /usr/local/bin -type l -exec ls -l {} \;
You can run it straight away with rm, I just prefer the more conservative approach...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.