[Mesa-dev] [PATCH] Allow glTexImage2D with a depth component cube map

[Kenneth Graunke]

On 11/22/2011 03:34 PM, Anuj Phogat wrote:
> On Tue 22 Nov 2011 12:21:09 PM PST, Kenneth Graunke wrote:
>> On 11/22/2011 11:42 AM, Anuj Phogat wrote:
>> [snip]
>>>   I agree. This is simpler to read and _mesa_is_cube_map_face() can
>>> be reused
>>>   in mesa. Posting an updated patch with your suggestions.
>>>
>>>   >  I haven't tested this so the logic might be incorrect.
>>>   It worked as it is. Just defined a new function _mesa_is_cube_face().
>>
>> Actually, Brian already added that function; it's in teximage.h.
> 
> I just realised that my mesa branch was not updated with
> git://anongit.freedesktop.org/mesa/mesa.  _mesa_is_cube_face() do exist
> in teximage.h
> After fetching all the recent changes and installing libdrm 2.4.27, i am
> getting following error while building the mesa driver:
> 
> i830_state.c: In function ‘i830Enable’:
> i830_state.c:851:51: error: ‘struct intel_renderbuffer’ has no member
> named ‘region’
> gmake[6]: *** [i830_state.o] Error 1
> gmake[6]: *** Waiting for unfinished jobs....
> gmake[6]: Leaving directory
> `/home/anuj/projects/mesa/src/mesa/drivers/dri/i915'
> gmake[5]: *** [lib] Error 2
> gmake[5]: Leaving directory
> `/home/anuj/projects/mesa/src/mesa/drivers/dri/i915'
> gmake[4]: *** [subdirs] Error 1
> gmake[4]: Leaving directory `/home/anuj/projects/mesa/src/mesa/drivers/dri'
> gmake[3]: *** [default] Error 1
> gmake[3]: Leaving directory `/home/anuj/projects/mesa/src/mesa/drivers'
> gmake[2]: *** [driver_subdirs] Error 2
> gmake[2]: Leaving directory `/home/anuj/projects/mesa/src/mesa'
> make[1]: *** [subdirs] Error 1
> make[1]: Leaving directory `/home/anuj/projects/mesa/src'
> make: *** [default] Error 1
> 
> Is this a known issue or something specific to my system configuration?

Yep, Chad broke that yesterday when he pushed HiZ.  Oops.  Chad and Eric
are fixing it.

You don't need the i830/i915 drivers on your system anyway, so you can
just do 'make -i' to ignore it...or re-run configure and drop i830/i915
from your --with-dri-drivers.  It should be fixed shortly anyway.