Error while loading shared library that is already there

jesse_m · 04-25-2016, 09:32 PM

I am trying to install KiCAD (schematic and board editor).
My issue is that when I try to start the program I get the following error:

Code:

kicad: error while loading shared libraries: libwx_gtk2u_gl-3.1.so.1: cannot open shared object file: No such file or directory

However when I go to /usr/local/lib I can find that exact file with find:

Code:

$> find -name "libwx_gtk2u_gl*"
./libwx_gtk2u_gl-3.1.so.1.0.0
./libwx_gtk2u_gl-3.1.so
./libwx_gtk2u_gl-3.1.so.1

I am on Slackware current and this is how I installed everything:
Kicad is dependent on wxGTK3 and libgnomeprintui. I installed wxGTK3, libgnomeprintui, and their dependencies from slackbuilds. I had issues building libgnomeprint but found it was an issue with when it was building the docs so I built and installed gtk-doc and it seemed to install without errors after that, it said it installed successfully.

I realize that KiCAD might not be the most popular application to install but I wasn't sure if anyone has run into similar issues with shared libraries.

Thanks for any tips and pointers, I'm still a bit new to Slackware.

I am asking for help and not trying a lot of things because it takes a few hours to build KiCAD so I figured I would ask for help before trying to much else.

keefaz · 04-26-2016, 04:59 AM

You're in Slackware 32bits version?

How did you install wxPython? With slackbuild.org scripts, it should be installed in /usr not /usr/local

jesse_m · 04-27-2016, 06:14 AM

@keefaz
Thanks for the reply!
I'm on the 64 bit version.
I installed wxPython with the slack build script and the GNOMEPRINT=YES option:

Code:

sudo ./wxPython.SlackBuild GNOMEPRINT=YES
su -c "installpkg /tmp/wxPython-src-2.18.12.1.tgz"

I just tried uninstalling everything and trying again. I had built wxWidgets from source before and that may have messed something up so I'm going to try and clean that out and start again.

Emerson · 04-27-2016, 06:29 AM

Make sure /usr/local/lib is in /etc/ld.so.conf and run ldconfig by hand.

keefaz · 04-27-2016, 07:18 AM

Quote:

Originally Posted by jesse_m

@keefaz
Thanks for the reply!
I'm on the 64 bit version.

Yes, I asked because you found library files installed in /usr/local/lib
This place is for 32bits libraries
64bits libraries are installed in /usr/lib64 or /usr/local/lib64

Redo the wxPython installation with Slackbuild script and see if it solves Kicad install

As a side note, you could just install sbotools and run sboinstall kicad, which will install kicad taking care of the dependencies for you

sundialsvcs · 04-28-2016, 06:59 AM

The secret, as noted in post #4, is gonna be ldconfig.

Linux has a very-flexible module loading system, which permits applications to be very-generic or very-specific about what they want to load. It would be prohibitively time-consuming to search for the correct file every time, so Linux uses a "loader cache." ldconfig builds or rebuilds this cache-file, basically figuring-out in advance where "anything one could ask for" is located. At runtime, the loader never "searches." It relies upon the cache.

This command is ordinarily re-executed automatically, as part of the process of installing new libraries.