Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 09-03-2013, 01:27 PM   #1
Registered: Feb 2010
Distribution: Slackware
Posts: 184

Rep: Reputation: 22
cannot build Mesa with --enable-gbm and vsync doesn't work on cape verde gpu

Compiling Mesa 9.2 gives me this error:
  CC     s_atifragshader.lo
In file included from ../../../src/mesa/swrast/s_aatriangle.c:273:0:
../../../src/mesa/swrast/s_aatritemp.h: In function 'rgba_aa_tri':
../../../src/mesa/swrast/s_aatritemp.h:196:10: error: implicit declaration of function 'omp_get_thread_num' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
gmake[4]: *** [s_aatriangle.lo] Error 1
gmake[4]: *** Waiting for unfinished jobs....
^Cgmake[4]: *** [pack.lo] Error 1
gmake[3]: *** [all-recursive] Interrupt
gmake[2]: *** [all] Interrupt
gmake[1]: *** [all-recursive] Interrupt
make: *** [all-recursive] Interrupt
Using Slackware64 14 and installed glamor-egl and llvm-3.3 from slackware-current but always get this error. Also get it if I build with radeonsi driver support only.

Vsync doesn't even work with radeon driver and my cape verde GPU (radeon hd 7750). This is using a minimal Mesa-9.2 build without radeonsi or gbm build options.

Would appreciate any help!

Old 09-03-2013, 01:49 PM   #2
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 270

Rep: Reputation: 87
Going to head out on a limb here and say... some of the deps are out of date for that build on slackware-14.

A list of them are here:

may have better luck with -current if you need the newer mesa builds.
1 members found this post helpful.
Old 09-03-2013, 03:21 PM   #3
jon lee
Registered: Jul 2013
Posts: 111

Rep: Reputation: Disabled
What are your ./configure options? It works for me following the LFS configure. (Although I started out with slackware, I generally follow the lfs book to upgrade anything).

You do realize one of the bindings on mesa is qt, under some circumstances you may end up having to (re)compile qt and kde against your new mesa.
1 members found this post helpful.
Old 09-17-2013, 09:40 AM   #4
Registered: Feb 2010
Distribution: Slackware
Posts: 184

Original Poster
Rep: Reputation: 22
Rebuilt entire system from source but still can't get vsync working. Actually can't get direct rendering to work now. Keep getting this error
bash-4.2$ glxinfo | grep direct
Xlib:  extension "NV-GLX" missing on display ":0.0".
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
Forgot to mention before, I used to have nvidia proprietary drivers installed before using open source radeon drivers with my new radeon hd 7750 card. Looking around the net it seems many others have had similar, if not, the same problem, switching drivers this way. Archlinux users suggest completely purging nvidia-drivers and xorg modules but I have no idea how that translates to manual administration (ala LFS).

As a note, my Mesa dependencies are up to date according to the LFS link provided with Mesa-9.2.0. Also built system using xorg from Slackware-current (64-bit).

Appreciate the responses!

Wildwizard, thanks for your help from post below! That seems to have worked. Unfortunately, open source drivers for cape verde GPU's are extremely under-developed. It appears the radeonsi driver hangs with recent git repository (mesa) including older versions, and only software rendering works. Can get better performace and what seems to be hardware acceleration with basic radeon driver, but no vsync still persists.

Have reverted to FGLRX for the time being and finally found a program that can customize and output user made edid files. This is the best program I've found to do that; it's located here: It's for Windows but haven't found anything like it for Linux. FGLRX doesn't accept custom modelines in xorg.conf (maybe one if you're lucky). For the record, OpenCL performance is outstanding in FGLRX drivers and seems to be the best around.

Going to mark this thread as solved since mesa3d needs further development for radeonsi driver.


Last edited by Holering; 09-19-2013 at 01:51 AM.
Old 09-17-2013, 05:14 PM   #5
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 866

Rep: Reputation: 264Reputation: 264Reputation: 264
You can find nvidia contamination in the following locations :-


And don't forget the kernel driver in


Also if your multilib enabled check the same sites in /usr/lib
1 members found this post helpful.


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] Kernel-3.11-rc7 kms init causes system hang during boot with cape verde gpu. Only me? Holering Linux - Kernel 5 09-18-2013 09:41 AM
LXer: Why Mesa 9.2 Doesn't Work For All Linux Users LXer Syndicated Linux News 0 08-21-2013 10:51 PM
Mesa 7.7 in current causes rendering issues on Intel gpu jazzor Slackware 0 03-02-2010 06:21 AM
How to enable vsync? NTolerance Linux - General 0 04-10-2005 05:50 PM
how can i enable vsync Creeps Linux - General 0 09-30-2004 04:43 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:12 AM.

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