VitualGL-2.3.2 error on build on Slackware64-14.0 multilib
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.
Building CXX object server/fltk/CMakeFiles/fltk_static.dir/fl_symbols.cxx.o
[ 72%] [ 72%] Building CXX object server/fltk/CMakeFiles/fltk_static.dir/screen_xywh.cxx.o
Building C object server/fltk/CMakeFiles/fltk_static.dir/flstring.c.o
Linking CXX static library ../../lib/libfltk_static.a
[ 72%] Built target fltk_static
Linking CXX executable ../bin/fakerut
/usr/lib/libGL.so: could not read symbols: File in wrong format
collect2: error: ld returned 1 exit status
make: *** [bin/fakerut] Error 1
make: *** [server/CMakeFiles/fakerut.dir/all] Error 2
make: *** [all] Error 2
The Slackbuild was called with COMPAT32=yes, i have both mesa's package (i486 and the compat32 equivalent) from alien's bob repository which was built with glapi enabled.
What should i do to build this package?
it's looking for 64 bit OpenGL libs in /usr/lib, which has your 32-bit libs in it. A quick fix might be to make a quick backup of the /usr/lib/OpenGL libs, then symlink the openGL files from /usr/lib64 into /usr/lib, then replace the 32 bit files after finishing your Bumblebee setup.
There's probably a better way but that's the first thing that comes to mind and I'm in the middle of a class so I don't have time to help work you through a better solution.
The only libmesa packages you should have are the compat32 and the native x64 packages, not the i486. You might need to remove the i486 package entirely and reinstall the native x64 packages for libmesa.
When you install the 32-bit compatibility layer you should only install those libraries and packages AlienBOB lists on his FTP and no other packages, or you will have issues.
After you have restored your libmesa x64 packages, the compat32 packages, and cleaned up your system, follow the instructions here:
I cleaned up all my system and local sources, including multilib packages and downloaded it all again.
The http://docs.slackware.com/howtos:har...nvidia_optimus instructions has been updated and if VirtualGL is not a dependency anymore, I'll not use it.
It appears that i misplaced the mesa package with some wrong architecture/compat32 package.
Now i have these 2 mesa packages from alien multilib mirrors:
When it's done I'll post what happened here.
Those look right now. I just got the time to get the how-to updated today. The readme included in the bumblebee git was more up to date. I'm not sure why VirtualGL was marked in the how-to as a dependency, but as you see, that has all been corrected.
Have to tell you, once you see this really work... It is very cool :-)
Last edited by WhiteWolf1776; 07-17-2013 at 06:18 AM.
Yes, if you don't need VirtualGL don't build and install it. Primusrun works much better. I highly recommend you use the Nvidia proprietary driver rather than Nouveau as it tends to work a bit better for applications and the system in general at times.