Bug 5873 - Build error: `X_GLXvop_BindTexImageEXT' and `X_GLXvop_ReleaseTexImageEXT' undeclared
Summary: Build error: `X_GLXvop_BindTexImageEXT' and `X_GLXvop_ReleaseTexImageEXT' und...
Status: RESOLVED NOTABUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: GLX (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-13 17:12 UTC by Luis
Modified: 2009-08-24 12:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Luis 2006-02-13 17:12:19 UTC
glxcmds.c: In function `glXBindTexImageEXT':
glxcmds.c:2618: error: `X_GLXvop_BindTexImageEXT' undeclared (first use in this
function)
glxcmds.c:2618: error: (Each undeclared identifier is reported only once
glxcmds.c:2618: error: for each function it appears in.)
glxcmds.c: At top level:
glxcmds.c:2636: warning: no previous prototype for 'glXReleaseTexImageEXT'
glxcmds.c: In function `glXReleaseTexImageEXT':
glxcmds.c:2659: error: `X_GLXvop_ReleaseTexImageEXT' undeclared (first use in
this function)
make[3]: *** [glxcmds.o] Error 1
make[3]: Leaving directory `/home/luis/tmp/x11/Mesa/src/glx/x11'
make[2]: *** [subdirs] Error 1
make[2]: Leaving directory `/home/luis/tmp/x11/Mesa/src'
make[1]: *** [default] Error 1
make[1]: Leaving directory `/home/luis/tmp/x11/Mesa'
make: *** [linux-dri-x86] Error 2

Could only build Mesa using the prior CVS versions of glx_pbuffer.c, glxcmds.c,
glxextensions.c and glxextensions.h, found at:

http://cvs.freedesktop.org/mesa/Mesa/src/glx/x11/

System: slackware-current
Kernel: 2.6.15.4
GCC: 3.4.5

Please let me know if there's any additional info that might be useful.
Comment 1 Michel Dänzer 2006-02-13 21:08:16 UTC
You need glxproto.h from the X.Org proto/GL CVS module to build current Mesa CVS.
Comment 2 Adam Jackson 2009-08-24 12:23:42 UTC
Mass version move, cvs -> git


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.