Bugzilla – Bug 71397
[llvmpipe] configure: error: Package requirements (dri3proto >= 1.0) were not met
Last modified: 2016-03-31 10:40:29 UTC
mesa: f41c01c68847a2d3df8f3c8786ef803428a0be13 (master)
$ ./autogen.sh --with-dri-drivers= --with-gallium-drivers=swrast
checking for DRI2PROTO... yes
checking for DRI3PROTO... no
configure: error: Package requirements (dri3proto >= 1.0) were not met:
No package 'dri3proto' found
Author: Keith Packard <firstname.lastname@example.org>
Date: Mon Nov 4 18:15:51 2013 -0800
Add DRI3+Present loader
Uses the __DRIimage loader interfaces.
v2: Fix _XIOErrors when DRI3 isn't present (change by anholt). Apparently
XCB just terminates your connection if you don't check for extensions
before using them, instead of returning an error like you'd expect.
Signed-off-by: Keith Packard <email@example.com>
Reviewed-by: Kristian Høgsberg <firstname.lastname@example.org>
Reviewed-by: Eric Anholt <email@example.com>
Does http://lists.freedesktop.org/archives/mesa-dev/2013-November/048072.html fix your issue? Note that you have to use --disable-dri3
Created attachment 88912 [details] [review]
v2 --disable-dri3 Patch
I had to use the modified version of the original that I attached here.
I've just tested this with the following command line:
$ autogen.sh --prefix=/usr/local --libdir=/usr/local/lib64 --with-gallium-drivers=r600 --with-llvm-shared-libs --with-dri-drivers= --enable-texture-float --enable-64-bit --disable-dri3
On Ubuntu «sudo apt-get build-dep libegl1-mesa» fixed the problem. Here's the list of installed packages, so that people from other distros could figure out what are they probably need:
libmirprotobuf0 libelf-dev libprotobuf-lite8 libprotobuf-dev libmirprotobuf-dev mircommon-dev libvdpau-dev x11proto-dri3-dev:all 1.0-1 x11proto-present-dev:all 1.0-1 libmirclient7 libmirclient-dev libmirclientplatform-mesa libc-bin
> Does http://lists.freedesktop.org/archives/mesa-dev/2013-November/048072.html
> fix your issue? Note that you have to use --disable-dri3
Oh, c'mon, how could anyone seriously choose that as a solution?? First I stumbled upon just that mailing list, and I were almost sure it is a mockery — the more surpise to me that the OP accepted it. Let me explain if that is unclear: the mentioned switch forces usage of a previous DRI version instead of DRI3, you almost definitely don't want this.