Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 513166 - x11-drivers/xf86-video-intel-2.99.912 with x11-base/xorg-server-1.14.7 - conftest.c:54:2: error: #error DRI3 not defined
Summary: x11-drivers/xf86-video-intel-2.99.912 with x11-base/xorg-server-1.14.7 - conf...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-14 01:17 UTC by Maciej Piechotka
Modified: 2015-02-23 01:03 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
x11-drivers:xf86-video-intel-2.99.912:20140614-005333.log.gz (x11-drivers:xf86-video-intel-2.99.912:20140614-005333.log.gz,6.18 KB, application/x-gzip)
2014-06-14 01:17 UTC, Maciej Piechotka
Details
config.log (config.log,83.38 KB, text/plain)
2014-06-14 13:38 UTC, Maciej Piechotka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Piechotka 2014-06-14 01:17:04 UTC
Created attachment 378844 [details]
x11-drivers:xf86-video-intel-2.99.912:20140614-005333.log.gz

checking whether to include DRI3 support... no
configure: error: DRI3 requested but prerequisites not found

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.912/work/xf86-video-intel
-2.99.912_build/config.log
 * ERROR: x11-drivers/xf86-video-intel-2.99.912::gentoo failed (configure phase)
:

From config.log:

configure:20667: x86_64-pc-linux-gnu-gcc -std=gnu99 -c -O2 -march=native -pipe -
ggdb -Wa,--compress-debug-sections -I/usr/include/xorg  conftest.c >&5
conftest.c:54:2: error: #error DRI3 not defined
 #error DRI3 not defined
  ^
configure:20667: $? = 1
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-06-14 01:31:08 UTC
Quoting your build log:

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.912/work/xf86-video-intel-2.99.912_build/config.log
Comment 2 Maciej Piechotka 2014-06-14 13:38:05 UTC
Created attachment 378880 [details]
config.log

Full config log. The failure is attached above - the DRI3 macro is not defined in xorg-server.h which belongs to x11-base/xorg-server.
Comment 3 Maciej Piechotka 2014-06-14 13:39:39 UTC
(In reply to Maciej Piechotka from comment #2)
> Created attachment 378880 [details]
> config.log
> 
> Full config log. The failure is attached above - the DRI3 macro is not
> defined in xorg-server.h which belongs to x11-base/xorg-server.

Just as a side note - I do have x11-proto/dri3proto and x11-proto/presentproto.
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2014-06-14 21:58:17 UTC
x11-drivers/xf86-video-intel-2.99.912 already properly DEPENDs on x11-proto/dri3proto
Comment 5 Chí-Thanh Christopher Nguyễn gentoo-dev 2014-06-15 19:38:23 UTC
xorg-server-1.14 does not have dri3 support yet, and dri3 is automagic in xf86-video-intel.

We will either have to raise the dependency, or find a way to explicitly disable dri3 in the intel driver.
Comment 6 Rémi Cardona (RETIRED) gentoo-dev 2014-06-15 21:31:22 UTC
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=7bc669dd4b7e3e5978e95e4131d1f9215afbc041

http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=5a0cb1049c2fa0586708719210a2d2cffa7a4491

Once these 2 land in a release (or if we decide to patch .912), we can then decide what to do with dri3 and present (USE flag, force on or off).
Comment 7 Jacob Godserv 2014-06-17 13:52:57 UTC
Would it be proper to mask until fix is available?
Comment 8 Chí-Thanh Christopher Nguyễn gentoo-dev 2014-06-17 13:59:29 UTC
(In reply to Jacob Godserv from comment #7)

I don't think so. If you run latest unstable xorg-server and xf86-video-intel, you will not be affected. Only users who choose to mix latest unstable xf86-video-intel with older xorg-server will see this issue.
Comment 9 Matt Turner gentoo-dev 2015-02-23 01:03:12 UTC
I think it's very likely this is fixed in a new version of the driver. If it's
not, please file a bug upstream at bugs.freedesktop.org. We're not prepared to
fix driver issues that aren't fixed upstream.