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.
Hello!
I am posting to share my experience with compiling texlive2009 from slackbuilds.org with xindy on 13.1. I need xindy for my documents so I had no option but to solve the issue.
I turned out that I had to remove clisp, install libsigsegv with the option "--enable-shared", then build clisp without libsigsegv (the stock clisp ships with libsigsegv built in), and then texlive2009 compiles ok.
In case somebody is interested I could post the scripts.
Maybe it would be better if Slackware shipped with libsigsegv compiled with shared libraries? xindy is really important for non latin alphabets.
Huge delay here, but I mentioned this to Pat, and here's some discussion:
{This is Pat talking}
I looked into that report about xindy... the real issue there is that xindy tries to build its own copy of clisp (used only to compile xindy), and so it runs into the same issues you'd expect trying to compile clisp. The deps for it are there, but because libsigsegv is not a shared library it passes --ignore-absence-of-libsigsegv to clisp, but picks up sigsegv.h anyway and blows up. Our external clisp would work fine, but the ./configure options for that do not work. Even after finding the correct options by reading the configure script (./configure --help outputs incorrect options).
My conclusion is that xindy is broken, and it's not up to me to work around it by compiling clisp in a less efficient way, or needlessly introducing another shared library. I'm putting it aside for now as not our bug. I suspect if xindy were patched to pass options to clisp that are similar to ours, then it would work. Untested.
... ( a bit later ) ...
It's easier than that, actually. A one-line diff does the trick.
- #include <sigsegv.h>
{End Pat talking}
So, in essence, remove the include of sigsegv.h and all should be fine with building xindy.
It is texlive2010 that is in question. If you need xindy I can tell you what I have currently done to get round this. I could also send you my build scripts. Robby's SlackBuild in slackbuilds.org is flawless, however it does not build xindy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.