SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It looks like you are using a 32-bit version of an open source software on Slackware64. That is not making sense.
The only reason for needing a multilib setup is if you have proprietary 32-bit software that you can't live without, or if you want to run 32-bit MS Windows programs under Wine.
For all other cases, you should just compile a 64-bit package out of the sources.
Ah! kicad is a major,major PITA to compile, certainly in 64 bit. That kind of rules it out. It relies tetotally on wxwidgets, and you get compile errors in kicad which originate in wxwidgets, so I spent an afternoon farting with this (fortunately making .txz packages so I could retreat with dignity)recompiling both. Then I did what they told me to, installed precompiled binaries.
So whoever compiled that had his 32bit libs in /usr/lib64?
32 bit compatibility should be taken more seriously. Another example of it is mesa, which even has a --enable-64bit-libs and --enable-32-bit-libs type switches, but specify both, and you're snookered.
The problem is caused by /etc/X11/xinit/xinitrc.xfce by overriding the built-in defaults of GTK:
# Export GTK_PATH so that GTK+ can find the Xfce theme engine
Comment it out and voila: GTK loads the correct theme engine for every ABI.
BTW: The GLADE-Stuff in xinitrc.xfce looks also very bogus. It sets GLADE_MODULE_PATH and others to ":" and breaks LIBGLADE_MODULE_PATH for multilib in the same way as GTK. Scripts like this trying to do fancy stuff should be inspected. There environment variables aren't needed at all.