LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-15-2013, 08:25 PM   #1
frushiyama
Member
 
Registered: Oct 2010
Location: Brazil
Distribution: Slackware64 14.1, Slackware ARM
Posts: 47

Rep: Reputation: 0
VitualGL-2.3.2 error on build on Slackware64-14.0 multilib


I'm following http://docs.slackware.com/howtos:har...nvidia_optimus, all others packages was builted fine, but i'm stacked on this error:
Code:
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[2]: *** [bin/fakerut] Error 1
make[1]: *** [server/CMakeFiles/fakerut.dir/all] Error 2
make: *** [all] Error 2
root@R500VD-BS71:/usr/src/Bumblebee-SlackBuilds/VirtualGL#
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?
 
Old 07-16-2013, 12:50 PM   #2
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 222

Rep: Reputation: 52
if primus built, I wouldn't worry about VirtualGL. It is quite a bit slower anyway.

Did you build the nvidia packages with COMPAT32=yes?
 
Old 07-16-2013, 02:41 PM   #3
Cultist
Member
 
Registered: Feb 2010
Location: Chicago, IL
Distribution: Slackware64 14.1
Posts: 777

Rep: Reputation: 101Reputation: 101
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.
 
Old 07-16-2013, 07:34 PM   #4
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 222

Rep: Reputation: 52
Had a bit more time to look into this... and it's driving me nuts. Can you give the version and location of what mesa packages you installed?

I built this just a few weeks ago and it worked fine. Started with VirtuaGL as I didn't want to mess with mesa updates.. but primus was so much faster I just use that now. Still, I expect it to work.

There has to be something wonky with the mesa you are using... just not sure what or why yet.
 
Old 07-16-2013, 08:38 PM   #5
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0, CRUX 3.1
Posts: 3,041
Blog Entries: 15

Rep: Reputation: 764Reputation: 764Reputation: 764Reputation: 764Reputation: 764Reputation: 764Reputation: 764
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:

http://docs.slackware.com/howtos:har...nvidia_optimus

To get BumbleBee working for your Nvidia Optimus card. Make sure you follow the instructions EXACTLY as written, or else it will not work at all.
 
Old 07-16-2013, 09:35 PM   #6
frushiyama
Member
 
Registered: Oct 2010
Location: Brazil
Distribution: Slackware64 14.1, Slackware ARM
Posts: 47

Original Poster
Rep: Reputation: 0
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:
mesa-8.0.4-x86_64-1
mesa-compat32-8.0.4-x86_64-1compat32
When it's done I'll post what happened here.
 
Old 07-16-2013, 09:43 PM   #7
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 222

Rep: Reputation: 52
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.
 
Old 07-16-2013, 10:34 PM   #8
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0, CRUX 3.1
Posts: 3,041
Blog Entries: 15

Rep: Reputation: 764Reputation: 764Reputation: 764Reputation: 764Reputation: 764Reputation: 764Reputation: 764
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.
 
Old 07-21-2013, 09:32 PM   #9
frushiyama
Member
 
Registered: Oct 2010
Location: Brazil
Distribution: Slackware64 14.1, Slackware ARM
Posts: 47

Original Poster
Rep: Reputation: 0
Bumblebee is working fine now, followed http://docs.slackware.com/howtos:har...nvidia_optimus instructions of instalation.
VirtualGL is not a depence anymore, so i'll not install it.
Tks for all help.
 
  


Reply

Tags
optimus


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Multilib issue: error upgrading glibc. System unusable. Slackware64 current val3xiv Slackware 2 05-21-2013 07:20 AM
[ANN] mk-slack64-multilib : A tool to create slackware64+multilib tree/iso phenixia2003 Slackware 5 12-28-2012 05:42 AM
Slackware64 multilib compile error Breeze Slackware 7 05-22-2011 02:56 AM
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
Slackware64-13.0 multilib can not build valid initrd for kernels 2.6.30 sid77 Slackware 11 03-03-2010 03:32 AM


All times are GMT -5. The time now is 04:07 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration