libGLEW.so.1.9: can't open shared object file: No such file
-
- Posts: 8
- Joined: Thu 23 Oct 2014, 16:49
libGLEW.so.1.9: can't open shared object file: No such file
How can I get this system to find GLEW? I have installed it multiple times and get the same error message.
Move these to /usr/lib. If you uncover more that's missing, see here.
- Attachments
-
- wrong_folder.jpg
- (19.44 KiB) Downloaded 317 times
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
-
- Posts: 8
- Joined: Thu 23 Oct 2014, 16:49
-
- Posts: 328
- Joined: Wed 25 Jun 2014, 20:31
Library files usually go into the /usr/lib folder. This is where most programs will look for them. But some packages (especially from other Linux distros) install their files elsewhere, often in subfolders of /usr/lib. This is usually what has happened when a program still complains that a library is missing after you installed it.
In this case, it seems that the files are in /usr/lib/i386-linux-gnu, as Semme's screenshot shows. Move them up to /usr/lib so that your program can find them.
- if you are using the ROX file manager, go into /usr/lib; it'll normally show newly-created files and folders in bold text
- open the package with an archive program to see which files are inside and which file paths they have
- use the file search (probably at Menu > Filesystem > Pfind)
In this case, it seems that the files are in /usr/lib/i386-linux-gnu, as Semme's screenshot shows. Move them up to /usr/lib so that your program can find them.
There are several ways to find out where a package has installed them:Glorfindel wrote:move them from where?
- if you are using the ROX file manager, go into /usr/lib; it'll normally show newly-created files and folders in bold text
- open the package with an archive program to see which files are inside and which file paths they have
- use the file search (probably at Menu > Filesystem > Pfind)
-
- Posts: 8
- Joined: Thu 23 Oct 2014, 16:49