From: Chad Versace <chad.versace@linux.intel.com>
To: sedat.dilek@gmail.com
Cc: mesa-dev@lists.freedesktop.org, DRI <dri-devel@lists.freedesktop.org>
Subject: Re: [Mesa-dev] mesa/gles3: dri_util.c:192:10: error: use of undeclared identifier '__DRI_API_GLES3'
Date: Thu, 24 Jan 2013 10:31:06 -0800 [thread overview]
Message-ID: <51017DEA.5030903@linux.intel.com> (raw)
In-Reply-To: <CA+icZUVW_RRe-x3wo5iXMz2MD+3WEPLJs7gKPrK7ubdSfsEY8Q@mail.gmail.com>
FYI,
The enum is defined in mesa iteself at
#MESA_SOURCE/include/GL/internal/dri_interface.h. Your
problem was independent of dri2proto, kernel, drm, etc. I expect
your build environment was accidentally #including the header located
in /usr/include/GL/internal rather than the one in the mesa source tree.
On 01/24/2013 04:33 AM, Sedat Dilek wrote:
> Hmm, switching to Ubuntu's distro-kernel, removing /opt/xorg and
> building the XORG stuff from scratch...
>
> 1. libdrm-git
> 2. mesa-git
> 3. xf86-video-intel-git
>
> ...makes the errors go away.
>
> OK, I had in my 3.8-rc4 kernel drm-intel-nightly integrated, but no
> linux-headers package of this kernel installed.
>
> Looks good.
>
> $ sudo grep -A4 'LoadModule: "intel"' /var/log/Xorg.0.log
> [ 15.913] (II) LoadModule: "intel"
> [ 15.913] (II) Loading
> /usr/lib/x86_64-linux-gnu/xorg/extra-modules/intel_drv.so
> [ 15.957] (II) Module intel: vendor="X.Org Foundation"
> [ 15.957] compiled for 1.11.3, module version = 2.20.19
> [ 15.957] Module class: X.Org Video Driver
>
> $ LIBGL_DEBUG=verbose glxinfo 2>/dev/null | grep -i opengl
> OpenGL vendor string: Intel Open Source Technology Center
> OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile
> OpenGL version string: 3.0 Mesa 9.1-devel (git-6f3caaf) <--- VERSION 3.0!
> OpenGL shading language version string: 1.30
> OpenGL extensions:
>
> - Sedat -
>
> On Thu, Jan 24, 2013 at 11:14 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> Hi Ian,
>>
>> due to the changes in...
>>
>> e90c08e dri: Define enum __DRI_API_GLES3
>>
>> ...I get this breakage with mesa-gles3-git6f3caaf:
>>
>> make[7]: Entering directory
>> `/home/wearefam/src/mesa/mesa-git/src/mesa/drivers/dri/common'
>> CC utils.lo
>> CC dri_util.lo
>> CC libdri_test_stubs_la-dri_test.lo
>> CC xmlconfig.lo
>> CCLD libdri_test_stubs.la
>> dri_util.c:192:10: error: use of undeclared identifier '__DRI_API_GLES3'
>> case __DRI_API_GLES3:
>> ^
>> 1 error generated.
>> make[7]: *** [dri_util.lo] Error 1
>>
>> Do I need a different DRI/DRI2 proto?
>> From which fdo GIT tree?
>> If YES, can you bump the required version in configure.ac?
>>
>> Thanks!
>>
>> Regards,
>> - Sedat -
>>
>> P.S.: Check installed DRI/DRI2 proto version
>>
>> $ dpkg -l | grep dri | grep proto | grep -e \-dev
>> ii x11proto-dri2-dev 2.8-1~precise1
>> X11 DRI2 extension wire protocol
>>
>> - EOT -
> _______________________________________________
> mesa-dev mailing list
> mesa-dev@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
next prev parent reply other threads:[~2013-01-24 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 10:14 mesa/gles3: dri_util.c:192:10: error: use of undeclared identifier '__DRI_API_GLES3' Sedat Dilek
2013-01-24 12:33 ` Sedat Dilek
2013-01-24 18:31 ` Chad Versace [this message]
2013-01-24 19:10 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51017DEA.5030903@linux.intel.com \
--to=chad.versace@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mesa-dev@lists.freedesktop.org \
--cc=sedat.dilek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox