a question on texlive's kpathsea and LD_LIBRARY_PATH
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.
a question on texlive's kpathsea and LD_LIBRARY_PATH
Dear Slackers,
I recently installed a Slackware-13.1 32 bit system and I encountered an odd problem.
I had a texlive-2010 package from slackbuilds.org, previously compiled on another 32 bit Slack-13.1 system. I just installed the precompiled package on the new system. However, whenever I tried to issue a latex command, kpathsea complained that it cannot find the shared library file libkpathsea.so.6. I googled a bit and I found that this could be circumvented by setting the environment variable LD_LIBRARY_PATH to "/usr/share/texmf/lib", where the library in question actually is. This solved the problem. The weird thing is that on other machines I have installed, kpathsea had no issues whatsoever and I did not have to set the LD_LIBRARY_PATH. The only difference is that on those systems I had compiled and installed texlive, not just installing a precompiled package. Could that be causing the issue?
John, you were right. I did a little investigation on my machine at home where I compiled the package and where kpathsea found what it needed. Here are the results:
Obviously on this machine the problem did not occur just because I still have not deleted the directory /home/marto/build/tmp/texlive-20100722-source, where I compiled texlive-2010. How can I make the system search for libkpathsea in /usr/share/texmf/lib instead in /home/marto/build/tmp/texlive-20100722-source/inst/lib/? Maybe I have to manually edit the /etc/ld.so.conf file?
Obviously on this machine the problem did not occur just because I still have not deleted the directory /home/marto/build/tmp/texlive-20100722-source, where I compiled texlive-2010. How can I make the system search for libkpathsea in /usr/share/texmf/lib instead in /home/marto/build/tmp/texlive-20100722-source/inst/lib/? Maybe I have to manually edit the /etc/ld.so.conf file?
Well, it's a bit disturbing that the compiled binaries still search the build directory paths - that shouldn't happen (darn it, another thing to investigate later), but the problem you're encountering is my fault. I haven't confirmed this for sure, but it seems that the TeXLive 2009 stuff statically linked libkpathsea while 2010 links it dynamically. Since I didn't notice that, I failed to copy the shared library into the package directory. I attached a (probably) correct build script to the mail I sent, and assuming it is indeed correct, I'll get that into the SBo git repo tomorrow.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.