LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
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 12-02-2016, 07:41 AM   #1
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 119

Rep: Reputation: 58
TexLive doesn't read my ~/texmf after the upgrading to 2016


Hey all,

I'm kind of lost here. I upgraded TexLive to the 2016 version from SlackBuilds. Now it refuses to read my custom .sty and .cls files in ~/texmf/tex/latex.

I checked my environment: $TEXMFHOME isn't set and therefor should default to ~/texmf. I also tried to explicitly set $TEXMFHOME, which didn't solve the problem.

Further I tried to copy the .cls and .sty files to /usr/share/texmf-local, running rehash and compiling the document. No change here.

Any ideas what I'm missing here. These are the environment variables that are relevant to TeX. I didn't set TEXMFCACHE but unsetting it doesn't help.

Code:
$ env | grep TEX
TEXMF=/usr/share/texmf-dist
TEXMFCACHE=/home/<myuser>/.texmf-cache
TEXMFLOCAL=/usr/share/texmf-local
TEXMFHOME=/home/<myuser>/texmf
Whenever I try to compile a Latex-File using a custom class or style file, I get the following error:

Code:
! LaTeX Error: File `<mycustomfile>.sty' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: sty)

Enter file name:
 
Old 12-03-2016, 04:00 AM   #2
aragorn2101
Member
 
Registered: Dec 2012
Location: Mauritius
Distribution: Slackware
Posts: 567

Rep: Reputation: 301Reputation: 301Reputation: 301Reputation: 301
Hi,

Maybe the cache was not updated properly, try

Code:
texhash ~/texmf
 
Old 12-03-2016, 04:10 AM   #3
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 119

Original Poster
Rep: Reputation: 58
Quote:
Originally Posted by aragorn2101 View Post
Hi,

Maybe the cache was not updated properly, try

Code:
texhash ~/texmf
I already tried this, it doesn't help. With TexLive 2015 it wasn't even required to run texhash over TEXMFHOME as long as you kept the files in the correct folders. I wasn't able to find any info that this changed in the 2016 version.
 
Old 12-03-2016, 04:52 AM   #4
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 535

Rep: Reputation: 379Reputation: 379Reputation: 379Reputation: 379
Quote:
Originally Posted by navigium View Post
I already tried this, it doesn't help. With TexLive 2015 it wasn't even required to run texhash over TEXMFHOME as long as you kept the files in the correct folders. I wasn't able to find any info that this changed in the 2016 version.
What is your output from
Code:
kpsewhich -var-value TEXMFHOME
?
 
1 members found this post helpful.
Old 12-05-2016, 01:42 PM   #5
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 858

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
I'm having similar problems. TexLive now refuses to recognize a font I had installed several years ago and it is in my systemwide $TEXMFLOCAL path (/usr/share/texmf-local/). THis is even despite I ran texhash several times.

@franzen by the way, running the command you suggest in my system gaves the output ~/texmf/. I have my local user-specific config in ~/.texmf/. How could I fix this?

Thanks!
 
Old 12-05-2016, 02:23 PM   #6
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 858

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Even more: texlive does not read the contents of the $TEXMFLOCAL directory.

I even went as far as manually editing /usr/share/texmf-dist/web2c/updmap.cfg and add the relevant font map. At the next updmap-sys run, it generated an error message:

Code:
root:/home/eduardo]# updmap-sys
updmap will read the following updmap.cfg files (in precedence order):
  /usr/share/texmf-dist/web2c/updmap.cfg
updmap may write changes to the following updmap.cfg file:
  /usr/share/texmf-config/web2c/updmap.cfg
dvips output dir: "/usr/share/texmf-var/fonts/map/dvips/updmap"
pdftex output dir: "/usr/share/texmf-var/fonts/map/pdftex/updmap"
dvipdfmx output dir: "/usr/share/texmf-var/fonts/map/dvipdfmx/updmap"
updmap [ERROR]: The following map file(s) couldn't be found:
updmap [ERROR]:         myfontfile.map (in /usr/share/texmf-dist/web2c/updmap.cfg)
updmap [ERROR]: Did you run mktexlsr?

        You can disable non-existent map entries using the option
          --syncwithtrees.
The problem is, that .map file is on $TEXMFLOCAL, and I did run mktexlsr several times. Even more: the relevant directory where the .map file is stored has its relevant ls-R file with a timestamp of today.

If you could give any help in fixing this I'd be very grateful.
 
Old 12-05-2016, 02:55 PM   #7
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 535

Rep: Reputation: 379Reputation: 379Reputation: 379Reputation: 379
Quote:
Originally Posted by sombragris View Post
I'm having similar problems. TexLive now refuses to recognize a font I had installed several years ago and it is in my systemwide $TEXMFLOCAL path (/usr/share/texmf-local/).
What do you mean with "now"? Did it work with texlive2016 before the last update?

Quote:
@franzen by the way, running the command you suggest in my system gaves the output ~/texmf/. I have my local user-specific config in ~/.texmf/. How could I fix this?
The global runtime path configuration file for kpathsea is
/usr/share/texmf-dist/web2c/texmf.cnf
Put your changes -- and only your changes, not an entire copy! -- in
/usr/share/texmf.cnf
 
1 members found this post helpful.
Old 12-05-2016, 04:10 PM   #8
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 858

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Quote:
Originally Posted by franzen View Post
What do you mean with "now"? Did it work with texlive2016 before the last update?
I'm not certain about the last update, but IIRC it worked with at least the next to last. (that is, I think it was the last one you offered directly via LQ).
 
Old 12-05-2016, 04:18 PM   #9
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 858

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Quote:
Originally Posted by franzen View Post
The global runtime path configuration file for kpathsea is
/usr/share/texmf-dist/web2c/texmf.cnf
Now, this is odd.

in the global /usr/share/texmf-dist/web2c/texmf.cnf is this:

Code:
TEXMFROOT = $SELFAUTODIR/share

[snip]

% The main tree of distributed packages and programs:
TEXMFDIST = $TEXMFROOT/texmf-dist

[snip]

% Local additions to the distribution trees.
TEXMFLOCAL = $TEXMFROOT/texmf-local
All the variables are OK; they have the values expected from them. However, this one:

Code:
TEXMFLOCAL = $TEXMFROOT/texmf-local
is directly not honored by TeX; and maybe other paths aren't, either.

I don't have any custom texmf.cnf files anywhere.

Last edited by sombragris; 12-05-2016 at 04:19 PM.
 
Old 12-05-2016, 05:31 PM   #10
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 858

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
To be more specific: my map file is correctly located at /usr/share/texmf-local/fonts/map/dvips (i.e., $TEXMFLOCAL/fonts/map/dvips) but it is not picked up by updmap-sys.

I also see that the ls-R corresponding to the $TEXMFLOCAL directory correctly picks my map file. But somehow updmap fails to pick it.

Last edited by sombragris; 12-05-2016 at 05:36 PM. Reason: updates for clarification
 
Old 12-05-2016, 11:50 PM   #11
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 119

Original Poster
Rep: Reputation: 58
Quote:
Originally Posted by franzen View Post
What is your output from
Code:
kpsewhich -var-value TEXMFHOME
?
I wasn't able to check this earlier since I didn't have the machine with me. The output looks correct to me:

Code:
& kpsewhich -var-value TEXMFHOME
/home/<my user>/texmf
I'm really lost here as it worked with the previous version. Maybe I should try to downgrade. Is there a way to access previous versions of Slackbuilds?
 
Old 12-06-2016, 04:06 AM   #12
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 535

Rep: Reputation: 379Reputation: 379Reputation: 379Reputation: 379
Quote:
Originally Posted by navigium View Post
I'm really lost here as it worked with the previous version. Maybe I should try to downgrade. Is there a way to access previous versions of Slackbuilds?
There's no official support to downgrade, you may go through slackbuild.org's cgit.
texlive2015 was never part of SBo, texlive2014 was there before.
I'll create a testcase to reproduce your issue, but i don't know if i find time today ...
 
Old 12-06-2016, 12:06 PM   #13
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 119

Original Poster
Rep: Reputation: 58
Quote:
Originally Posted by franzen View Post
There's no official support to downgrade, you may go through slackbuild.org's cgit.
texlive2015 was never part of SBo, texlive2014 was there before.
I'll create a testcase to reproduce your issue, but i don't know if i find time today ...
Honestly, I'm not sure whether you'll be able to reproduce my problem. I've got two more or less identical Slackware 14.2 installs and it only happens on one box. I couldn't figure out the difference yet.
 
Old 12-06-2016, 01:23 PM   #14
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 535

Rep: Reputation: 379Reputation: 379Reputation: 379Reputation: 379
Quote:
Originally Posted by navigium View Post
Honestly, I'm not sure whether you'll be able to reproduce my problem. I've got two more or less identical Slackware 14.2 installs and it only happens on one box. I couldn't figure out the difference yet.
Maybe the arch-wiki about texlive can help.
If nothing helps, i suggest to save you texlive-config/styles/whatever, then
Code:
removepkg /var/log/packages/tetex*
removepkg /var/log/packages/texlive*
rm -rf /usr/share/texmf*
rm -rf /home/<my user>/texlive*
rm -rf /home/<my user>/.tex*
unset TEXMF
then install texlive2016 again, and put back in your files and test step-by-step.
 
1 members found this post helpful.
Old 12-07-2016, 01:22 AM   #15
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 119

Original Poster
Rep: Reputation: 58
Quote:
Originally Posted by franzen View Post
Maybe the arch-wiki about texlive can help.
If nothing helps, i suggest to save you texlive-config/styles/whatever, then
Code:
removepkg /var/log/packages/tetex*
removepkg /var/log/packages/texlive*
rm -rf /usr/share/texmf*
rm -rf /home/<my user>/texlive*
rm -rf /home/<my user>/.tex*
unset TEXMF
then install texlive2016 again, and put back in your files and test step-by-step.
Thank you, this finally solved the problem. I did a reinstall before but obviously I didn't delete all the files removepkg left out.
 
  


Reply



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] texlive-texmf-docs compile fails canadensis Slackware 4 05-10-2015 03:56 PM
kertex (a new portable texmf system) vonbiber Linux - Software 0 03-11-2012 03:13 AM
update texlive (tlmgr): no texlive.tlpdb tramni1980 Slackware 3 03-30-2011 07:30 AM
slackbuild textlive on slackware 13 missing texmf tree balamkej Slackware 4 01-21-2010 03:19 PM
Example share in smb.conf doesn't work - read/write vs read only kleptophobiac Linux - Networking 0 09-01-2004 07:14 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:32 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration