LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-24-2013, 07:44 PM   #1
flokofcgulls
Member
 
Registered: Apr 2013
Posts: 79

Rep: Reputation: Disabled
texlive2013 in Slackware64-14.0 can only build documents as root, .sty not found


I downloaded the install DVD for texlive 2013, and installed it using their instructions.

There was a comment that they recommended installing it as a non-root user, but when I tried it complained that I didn't have permissions to write to /usr/local. I didn't want to modify the default, so I went ahead and installed it as root.

I wanted to test if it worked by building some documents from .tex files I had made a few months back. When I try to build them as myself, I get errors about .sty files missing, although I've verified that they're already installed. If I give the path to them, I'm met with more weird errors.

If I run pdflatex as root on the same document, it builds immediately with no errors. I thought it might be related to the permissions from earlier, so I ran chown recursively on the entire folder, but that had no effect on the problem, so I set it back to root:root.

And now...I'm not exactly sure how to fix it? The only searches I could find on it said to run mktexlsr, but this also had no effect. I'm still thinking it's related to something about installing as root, but I could be looking in the totally wrong direction.

Any ideas?
 
Old 07-24-2013, 09:16 PM   #2
qweasd
Member
 
Registered: May 2010
Posts: 449

Rep: Reputation: Disabled
I know nothing of texlive 2013, but just fyi, there is a slackbuild of texlive. This is the only TeX distro I use, and I can't complain.
 
Old 07-24-2013, 09:22 PM   #3
flokofcgulls
Member
 
Registered: Apr 2013
Posts: 79

Original Poster
Rep: Reputation: Disabled
I actually tried to build the slackbuild first, but it kept running out of space and failing, so I thought the DVD might be a better choice since it's such a big install.
 
Old 07-24-2013, 10:08 PM   #4
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,264

Rep: Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649Reputation: 649
Robby Workman has a pre-built package for TeX Live (and its dependency libsigsegv) at his repository, which is the best way to install it on Slackware in my opinion. It is the 2012 version though, so you're out of luck if you really need 2013.

Last edited by T3slider; 07-24-2013 at 10:11 PM.
 
Old 07-24-2013, 10:36 PM   #5
flokofcgulls
Member
 
Registered: Apr 2013
Posts: 79

Original Poster
Rep: Reputation: Disabled
Thanks for posting that, as far as I'm aware I don't really need 2013, honestly not even sure about the differences between them. If it will build my .tex documents I'm good to go.

I'll have to figure out how to uninstall the one I have first though...once I figure that out I'll report back.
 
Old 07-25-2013, 09:19 AM   #6
sairum
LQ Newbie
 
Registered: Sep 2004
Distribution: Slackware
Posts: 17

Rep: Reputation: 7
I'm using texlive2013 installed from the DVD with no issues in SW64-14 multilib. I've installed it as root as it goes into /usr/local/texlive/2013/. The only thing to do afterwards is, as a normal user, to update the PATH in .bashrc or .profile (export PATH=$PATH:/usr/local/texlive/2013/bin/x86_64-linux/). Apparently, you (user) may have some conflicting PATH variable, and root has not. Try to check the files above... or those residing at /etc/profile.d/

Antonio
 
Old 07-25-2013, 11:27 AM   #7
flokofcgulls
Member
 
Registered: Apr 2013
Posts: 79

Original Poster
Rep: Reputation: Disabled
I was just about to try the package in the repo that T3Slider mentioned, when I saw sairum's post about the PATH, so I decided to give it a try first.

As a side note, I found it was actually quite easy to uninstall texlive by running the command tlmgr uninstall, and then rm -r /usr/local/texlive, in case anyone finds it useful.

So I reinstalled it, and went to find the files sairum mentioned. I discovered that neither ~/.bashrc or ~/.profile existed on my system, the only one I had was ~/.bashrc_profile. This is my first time working with these files so I had to go read up on them a little bit, and I found another one called /etc/profile that did exist.

There was a line there for setting the default system $PATH, so I added /usr/local/texlive/2013/bin/x86_64-linux/ to the end of that line, and after logging out and back in, I tried to build a document again and it worked with no errors! I would be interested to know if this is considered a good practice or not, and if I would be better off creating one of the other files mentioned instead?

I found this surprising, because I had originally investigated a PATH issue before I opened this thread, and I saw that this location was not in root's PATH either, leading me to think the problem must lie elsewhere.

Even though I ended up not using it, the link to the repo with the pre-built package for texlive2012 is great to know about, and may very well come in handy in the future.
 
Old 07-28-2013, 10:46 AM   #8
ml4711
Member
 
Registered: Aug 2012
Location: Ryomgård, Danmark
Distribution: Slackware64
Posts: 84

Rep: Reputation: 39
Quote:
There was a line there for setting the default system $PATH, so I added /usr/local/texlive/2013/bin/x86_64-linux/ to the end of that line, and after logging out and back in, I tried to build a document again and it worked with no errors! I would be interested to know if this is considered a good practice or not, and if I would be better off creating one of the other files mentioned instead?
A more elegant way adding to PATH is by making
a your_script.sh in /etc/profile.d as all those scripts get sourced from /etc/profile.

Just read a few of the existing scripts, and you know what to do.

Changes you make to /etc/profile may get lost in an update.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware64 -current: w3m fails to build... andrew.46 Slackware 12 06-16-2013 01:05 AM
Slackware64 14.0 - X fails to start as non-root + Termination as root freezes sytem slaka Slackware 5 04-17-2013 04:46 AM
[SOLVED] Cannot build physfs-2.0.2 on slackware64 -current andrew.46 Slackware 2 04-09-2012 10:21 PM
[SOLVED] madwifi driver won;t build with slackware64 13.1 squid890 Linux - Wireless Networking 2 06-07-2010 04:46 PM
Cannot build extreme tuxracer Slackware64 mlangdn Slackware 12 06-21-2009 04:42 AM


All times are GMT -5. The time now is 10:19 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration