<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - make error with Gallium i915/DRM configuration" href="https://bugs.freedesktop.org/show_bug.cgi?id=75286#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - make error with Gallium i915/DRM configuration" href="https://bugs.freedesktop.org/show_bug.cgi?id=75286">bug 75286</a> from <a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>(In reply to <a href="show_bug.cgi?id=75286#c5">comment #5</a>) [snip] > I ship i915g on Chrome OS, so it is maintained. I don't encounter many > issues with it, though, so there's not many commits. As for i915 + sw > winsys, probably no one uses it. Maybe we should ask on the list. AFAICS you are the primary developer of i915 so it's only fair that you give the good news :-) (In reply to <a href="show_bug.cgi?id=75286#c6">comment #6</a>) > > (In reply to <a href="show_bug.cgi?id=75286#c3">comment #3</a>) [snip] > > dri does not imply X11 in this case. You should be able to run i915/drm on a > > X-less system. > > The latest configuration I tried was this one: > > ./configure --enable-gles2 --disable-glx --with-dri-drivers= > --enable-gallium-egl --with-egl-platforms=drm --with-gallium-drivers=i915 > > but it depends on X11 headers: > > ---------- > Making all in pipe-loader > make[3]: Entering directory > `/home/christian/projects/mesa/mesa/src/gallium/auxiliary/pipe-loader' > CC libpipe_loader_la-pipe_loader.lo > CC libpipe_loader_la-pipe_loader_sw.lo > In file included from pipe_loader_sw.c:34:0: > ../../../../src/gallium/include/state_tracker/xlib_sw_winsys.h:5:22: fatal > error: X11/Xlib.h: No such file or directory > ---------- > > Since I'm planning to derive the source files needed for the port from the > make output, ideally there shouldn't appear any files which depend on > anything X11-related. But in case there is no configuration which matches > this constraint, I could also try to filter these files out later or try add > such a configuration if this could be useful for others, too. For compilation purposes you will need the headers but as far as runtime is concerned you should be fine. Here is a snippet from nouveau_dri.so $ ldd /usr/lib/xorg/modules/dri/nouveau_dri.so linux-vdso.so.1 (0x00007fffb430a000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007faaa5096000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007faaa4e79000) libdl.so.2 => /usr/lib/libdl.so.2 (0x00007faaa4c75000) libdrm_nouveau.so.2 => /usr/lib/libdrm_nouveau.so.2 (0x00007faaa4a6d000) libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007faaa4861000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007faaa455d000) libm.so.6 => /usr/lib/libm.so.6 (0x00007faaa425b000) libc.so.6 => /usr/lib/libc.so.6 (0x00007faaa3eb3000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007faaa3c9d000) /usr/lib64/ld-linux-x86-64.so.2 (0x00007faaa5c74000)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>