Bug 934 - Cannot build "glxinfo" with Sun's version of GL
Summary: Cannot build "glxinfo" with Sun's version of GL
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: App/other (show other bugs)
Version: unspecified
Hardware: SPARC Solaris
: high normal
Assignee: Roland Mainz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-27 16:35 UTC by Roland Mainz
Modified: 2004-07-26 23:55 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Patch for 2004-07-27-trunk (1.78 KB, patch)
2004-07-27 16:49 UTC, Roland Mainz 		no flags Details | Splinter Review
View All

Description Roland Mainz 2004-07-27 16:35:39 UTC 
Cannot build "glxinfo" with Sun's version of GL. The build fails like this:
-- snip --
xc/programs/glxinfo% make
cc -xO4 -xbuiltin=%all -xlibmil -xstrconst -xarch=v8 -Xa -v -zlazyload
-zcombreloc -xstrconst -xildoff -mt    -I../.. -I../../exports/include   -Dsun
-Dsparc -DSVR4 -D__EXTENSIONS__   -DXTHREADS   -DXUSE_MTSAFE_API
-DXUSE_NETDB_R_API       -c  glxinfo.c
"glxinfo.c", line 184: undefined symbol: GL_MAX_RECTANGLE_TEXTURE_SIZE_NV
"glxinfo.c", line 184: non-constant initializer: op "NAME"
"glxinfo.c", line 187: undefined symbol: GL_MAX_TEXTURE_LOD_BIAS_EXT
"glxinfo.c", line 187: non-constant initializer: op "NAME"
cc: acomp failed for glxinfo.c
*** Error code 2
-- snip --
Comment 1 Roland Mainz 2004-07-27 16:46:26 UTC 
Taking myself...
Comment 2 Roland Mainz 2004-07-27 16:49:07 UTC 
Created attachment 532 [details] [review]
Patch for 2004-07-27-trunk
Comment 3 Roland Mainz 2004-07-27 16:55:10 UTC 
Patch checked-in...

/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.136; previous revision: 1.135
/cvs/xorg/xc/programs/glxinfo/glxinfo.c,v  <--  glxinfo.c
new revision: 1.3; previous revision: 1.2
Mailing the commit message to xorg-commit@pdx.freedesktop.org...

... marking bug as FIXED.

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.