<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - egl_gallium always requires libdrm"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75751#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - egl_gallium always requires libdrm"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75751">bug 75751</a>
from <span class="vcard"><a class="email" href="mailto:christian.prochaska@genode-labs.com" title="Christian Prochaska <christian.prochaska@genode-labs.com>"> <span class="fn">Christian Prochaska</span></a>
</span></b>
<pre><span class="quote">> > In my understanding, if '--disable-dri' is given, libdrm should neither be a
> > requirement of the configure script nor should it get linked/used if it is
> > available.</span >
>
<span class="quote">> --disable-dri disables DRI drivers.
> </span >
Currently, it also disables the DRM winsys for egl_gallium with the i915 driver
(see <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - make error with Gallium i915/DRM configuration"
href="show_bug.cgi?id=75286">bug 75286</a>).
So it seems there are different interpretations about what '--disable-dri'
actually means. 'configure --help' says 'enable DRI modules'. Perhaps 'modules'
should get renamed to 'drivers' then and perhaps the option renamed to
'--enable-dri-drivers' to make it more clear?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>