Skip to content
This repository has been archived by the owner on Jul 6, 2020. It is now read-only.

error libglew at 0.6.3 #213

Open
ftoledo opened this issue Mar 8, 2019 · 8 comments
Open

error libglew at 0.6.3 #213

ftoledo opened this issue Mar 8, 2019 · 8 comments

Comments

@ftoledo
Copy link

ftoledo commented Mar 8, 2019

ragnarok@ragnarok:~/AppImage$ ./VSXu-0.6.3.glibc2.17.AppImage
/tmp/.mount_4dKo7g/usr/bin/vsxu_launcher: error while loading shared libraries: libGLEW.so.1.13: cannot open shared object file: No such file or directory

I use debian stretch, my libglew has version 2.0.0-3+b1 , previous vsxu (0.6.2) works fine.

@desperateCoder
Copy link

desperateCoder commented Apr 1, 2019

same here...
Linux Mint Debian Edition 3

myUser@odin:~/Downloads$ uname -a
Linux odin 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux

I already tried to install the following packages via apt:
libglew2.0 - OpenGL Extension Wrangler - runtime environment
libglewmx-dev - OpenGL Extension Wrangler MX - development environment
libglewmx1.13 - OpenGL Extension Wrangler (Multiple Rendering Contexts)

What makes me really curious: why would VSXU search the shared object in /tmp/.mount_[whatever] ?!

Thanks in advance! If you need more information, just ask 😁

@joserpena
Copy link

Same here. Lubuntu 18.04.2.

@irontempura
Copy link

irontempura commented Jun 28, 2019

Hello,

Sorry for the late response, but I am only now reading your issue. If others run into the same problem, they may find value in this solution.

I believe the problem is VSXU's AppImage is expecting libGLEW 1.13 and 1.13 specifically. You should be able to correct this by creating a symbolic link between the request for 1.13 and your current libGLEW directory.

Kindly open Terminal and verify you have libGLEW installed:

sudo apt install glew-utils

Then:

locate LibGLEW

This should spit out an install directory for your most recent libGLEW installation. If this returns no results, you can manually verify libGLEW's directory by navigating to: usr/lib/x86_64-linux-gnu and search for: libGLEW

If libGLEW is installed, it should return a couple of files:
libGLEW.so.#.#
libGLEW.so.#.#.#

The # above will be different depending on your version. You want the file that doesn't have the extra number.

Example: If you have libGLEW 2.0 installed, you will see:
libGLEW.so.2.0
libGLEW.so.2.0.0

In this case, you want libGLEW.so.2.0. Pay attention to its full path. Open Terminal once again, and enter:

sudo ln -s /usr/lib/x86_64-linux-gnu/libGLEW.so.#.# /usr/lib/x86_64-linux-gnu/libGLEW.so.1.13

Remember to replace the # above with the respective libGLEW values you found in your search.

Example: Continuing with the libGLEW 2.0 example above, the correct instruction is:

sudo ln -s /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0 /usr/lib/x86_64-linux-gnu/libGLEW.so.1.13

This creates a symbolic link, so any application looking for libGLEW 1.13 specifically, knows to use your most recent libGLEW version. Hope this help.

@joserpena
Copy link

joserpena commented Jun 28, 2019 via email

@desperateCoder
Copy link

Hi @irontempura ,
thanks for your reply! The symbolic link did the trick, thanks!

In case other have the same problem, here is what i did:

locate libglew # don't be dumb like me, better type 'locate libGLEW' (see below)

this gave me the following:

/usr/share/doc/libglew2.0
/usr/share/doc/libglewmx-dev
/usr/share/doc/libglewmx1.13
/usr/share/doc/libglew2.0/changelog.Debian.amd64.gz
/usr/share/doc/libglew2.0/changelog.Debian.gz
/usr/share/doc/libglew2.0/copyright
/usr/share/doc/libglewmx-dev/changelog.Debian.gz
/usr/share/doc/libglewmx-dev/copyright
/usr/share/doc/libglewmx1.13/changelog.Debian.gz
/usr/share/doc/libglewmx1.13/copyright
/usr/share/lintian/overrides/libglewmx1.13
/var/lib/dpkg/info/libglew2.0:amd64.list
/var/lib/dpkg/info/libglew2.0:amd64.md5sums
/var/lib/dpkg/info/libglew2.0:amd64.shlibs
/var/lib/dpkg/info/libglew2.0:amd64.symbols
/var/lib/dpkg/info/libglew2.0:amd64.triggers
/var/lib/dpkg/info/libglewmx-dev:amd64.list
/var/lib/dpkg/info/libglewmx-dev:amd64.md5sums
/var/lib/dpkg/info/libglewmx1.13:amd64.list
/var/lib/dpkg/info/libglewmx1.13:amd64.md5sums
/var/lib/dpkg/info/libglewmx1.13:amd64.shlibs
/var/lib/dpkg/info/libglewmx1.13:amd64.symbols
/var/lib/dpkg/info/libglewmx1.13:amd64.triggers

That was qite dumb, since linux is case sensitive, if i had typed 'libGLEW' there would have been my files already, but ok, i took an extra step:
Since i didn't see any shared object (*.so file) i followed your instruction:

cd /usr/lib/x86_64-linux-gnu
ls -l | grep libGLEW

This gave me my desired output:

lrwxrwxrwx  1 root root       19 Sep 16  2016 libGLEWmx.so -> libGLEWmx.so.1.13.0
lrwxrwxrwx  1 root root       19 Sep 16  2016 libGLEWmx.so.1.13 -> libGLEWmx.so.1.13.0
-rw-r--r--  1 root root   477296 Sep 16  2016 libGLEWmx.so.1.13.0
lrwxrwxrwx  1 root root       16 Sep 18  2016 libGLEW.so.2.0 -> libGLEW.so.2.0.0
-rw-r--r--  1 root root   587888 Sep 18  2016 libGLEW.so.2.0.0

The fourth line was my file, it points to 2.0.0, so i created the symbolic link for libGLEW.so2.0:

sudo ln -s /usr/lib/x86_64-linux-gnu/libGLEW.so.2.0 /usr/lib/x86_64-linux-gnu/libGLEW.so.1.13

@joserpena
Copy link

joserpena commented Jun 29, 2019 via email

@irontempura
Copy link

Glad my suggestion helped you. And yes, as Unix is case sensitive you will get better results by capitalizing GLEW, as you discovered.

@desperateCoder
Copy link

Yes, looks quite neat!

I'd suggest to close this issue, since the solution is documented here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants