-
Notifications
You must be signed in to change notification settings - Fork 59
error libglew at 0.6.3 #213
Comments
same here... 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: 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 😁 |
Same here. Lubuntu 18.04.2. |
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:
Then:
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: 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: In this case, you want libGLEW.so.2.0. Pay attention to its full path. Open Terminal once again, and enter:
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:
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. |
Dear irontempura,
The email sent to [email protected] with subject
"Re: [vovoid/vsxu] error libglew at 0.6.3 (#213)"
will be delivered as soon as possible.
Your email address is automatically added to the
recipients 'whitelist'. This means for further
emails to [email protected], you will not receive a delivery
notification again.
TK MAILIAS
*************************************************
Looking for a way to Protect Your Identity and
for a great no-more-spam solution for your email
address [email protected]? Sign up for TK Mailias.
It's free! Please visit http://www.mail.tk/
|
Hi @irontempura , 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:
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:
This gave me my desired output:
The fourth line was my file, it points to 2.0.0, so i created the symbolic link for libGLEW.so2.0:
|
Dear Artur,
The email sent to [email protected] with subject
"Re: [vovoid/vsxu] error libglew at 0.6.3 (#213)"
will be delivered as soon as possible.
Your email address is automatically added to the
recipients 'whitelist'. This means for further
emails to [email protected], you will not receive a delivery
notification again.
TK MAILIAS
*************************************************
Looking for a way to Protect Your Identity and
for a great no-more-spam solution for your email
address [email protected]? Sign up for TK Mailias.
It's free! Please visit http://www.mail.tk/
|
Glad my suggestion helped you. And yes, as Unix is case sensitive you will get better results by capitalizing GLEW, as you discovered. |
Yes, looks quite neat! I'd suggest to close this issue, since the solution is documented here. |
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.
The text was updated successfully, but these errors were encountered: