Arch Linux

OakRaider4Life

Member

Registered: 2012-02-08

Posts: 98

Building lib32-mesa-full after architecture migration

I am finishing up migrating my installation of Arch Linux from i686 architecture to x86_64, which has gone mostly smoothly. However, when attempting to build the lib32-mesa-full from the AUR, I get the error

configure: error: DRI driver directory 'r300' does not exist

The error message is correct; the PKGBUILD defines the DRI driver directory with the configure option

--with-dri-driverdir=/usr/lib32/xorg/modules/dri

and within that directory, there is no directory by the name of 'r300'. What doesn't make sense about that, is that r300 isn't supposed to be a directory-- it's a shared object file which is supposed to be being built with the lib32-mesa-full library, as defined in the pkgbuild by the

--with-dri-drivers=swrast,radeon,r200,r300,r600,i810,i915,i965,unichrome,mach64,mga,r128,savage,sis,tdfx

option.

I'm not very adept at compiling software, so please excuse me if I overlooked something obvious, but I can't quite figure out what's going on here.

Last edited by OakRaider4Life (2012-10-01 21:51:35)

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: Building lib32-mesa-full after architecture migration

'-with-dri-diverdir' is just OakRaider4Life's typo, the PKGBUILD has it spelled correctly.

https://aur.archlinux.org/packages.php?ID=40786 is out of date and somebody else (a couple months ago) pointed out that it doesn't compile on 64-bit (see the comments on the AUR page).

What' the difference between that AUR package and lib32-mesa from the repos?

Edit I mean I see that it's e.g. '--with-gallium-drivers=r300,r600,nouveau,swrast' and not '--with-dri-drivers' but does it work for you?

Last edited by karol (2012-10-01 21:28:42)

OakRaider4Life

Member

Registered: 2012-02-08

Posts: 98

Re: Building lib32-mesa-full after architecture migration

Thank you for catching that typo; I've edited my post to reflect the correction.

My understanding of the mesa-full package from the AUR is in addition to including the drivers for all the video cards (which I am aware is quite superfluous), is that it includes additional drivers which aren't built in by default, and might result in better video performance. Whether or not this is accurate, my real interest in compiling mesa from source is to compile with the USE_EXTERNAL_DXTN_LIB=1 option to use the proprietary s3tc library.

I suppose I can always try the lib32-mesa-full-i915 package and see if it will successfully build.

Last edited by OakRaider4Life (2012-10-01 22:01:20)