cvs compile broken

[James Hawkins]

Hey,

CVS compile is broken on my machine:

make[2]: Entering directory `/home/jhawkins/wine/dlls/wined3d'
gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include
-D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-gstabs+ -Wpointer-arith  -g -O2  -o arb_program_shader.o
arb_program_shader.c
gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include
-D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-gstabs+ -Wpointer-arith  -g -O2  -o baseshader.o baseshader.c
gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include
-D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-gstabs+ -Wpointer-arith  -g -O2  -o basetexture.o basetexture.c
gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include
-D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-gstabs+ -Wpointer-arith  -g -O2  -o cubetexture.o cubetexture.c
gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include
-D__WINESRC__  -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-gstabs+ -Wpointer-arith  -g -O2  -o device.o device.c
device.c: In function `process_vertices_strided':
device.c:5015: `GL_READ_ONLY' undeclared (first use in this function)
device.c:5015: (Each undeclared identifier is reported only once
device.c:5015: for each function it appears in.)
device.c:5033: `GL_WRITE_ONLY' undeclared (first use in this function)
device.c: In function `IWineD3DDeviceImpl_ProcessVertices':
device.c:5352: `GL_READ_ONLY' undeclared (first use in this function)
make[2]: *** [device.o] Error 1
make[2]: Leaving directory `/home/jhawkins/wine/dlls/wined3d'
make[1]: *** [wined3d] Error 2
make[1]: Leaving directory `/home/jhawkins/wine/dlls'
make: *** [dlls] Error 2

-- 
James Hawkins

[James Hawkins]

On 6/26/06, James Hawkins <truiken(a)gmail.com> wrote:
> Hey,
>
> CVS compile is broken on my machine:

Part two:

vertexbuffer.c: In function `IWineD3DVertexBufferImpl_PreLoad':
vertexbuffer.c:145: `GL_ARRAY_BUFFER' undeclared (first use in this function)
vertexbuffer.c:145: (Each undeclared identifier is reported only once
vertexbuffer.c:145: for each function it appears in.)
vertexbuffer.c: In function `IWineD3DVertexBufferImpl_Lock':
vertexbuffer.c:349: `GL_READ_WRITE' undeclared (first use in this function)
vertexbuffer.c:355: `GL_WRITE_ONLY' undeclared (first use in this function)
vertexbuffer.c:357: `GL_READ_ONLY' undeclared (first use in this function)
vertexbuffer.c:361: `GL_ARRAY_BUFFER' undeclared (first use in this function)
vertexbuffer.c: In function `IWineD3DVertexBufferImpl_Unlock':
vertexbuffer.c:381: `GL_ARRAY_BUFFER' undeclared (first use in this function)
make[2]: *** [vertexbuffer.o] Error 1
make[2]: Leaving directory `/home/jhawkins/wine/dlls/wined3d'

-- 
James Hawkins

[Andrew Talbot]

James Hawkins wrote:
> On 6/26/06, James Hawkins <truiken(a)gmail.com> wrote:
> > Hey,
> >
> > CVS compile is broken on my machine:

It sounds like gcc is not finding your GL headers. I gained mine by
installing Mesa. On my SUSE 10.1 system, they got installed
under /usr/include/GL/.

-- Andy.

[James Hawkins]

On 6/26/06, Andrew Talbot <Andrew.Talbot(a)talbotville.com> wrote:
> James Hawkins wrote:
> > On 6/26/06, James Hawkins <truiken(a)gmail.com> wrote:
> > > Hey,
> > >
> > > CVS compile is broken on my machine:
>
> It sounds like gcc is not finding your GL headers. I gained mine by
> installing Mesa. On my SUSE 10.1 system, they got installed
> under /usr/include/GL/.

hmm I don't think so.  Even if that were the case, we should still
handle it without user intervention.  I'm pretty sure it's a
versioning problem, because this has happened before (recently).  I'm
on a modified Red Hat 9 system.

-- 
James Hawkins

WoW broken for wine 0.9.16 Nvidia cards

Hi,

Just a quick question, WoW ( World of Warcraft ) was broken  (for Nvidia 
cards) with there latest software update. Is anybody working on fixing 
Wow (with Nvidia Cards) ( working fine with ATI ).

I just wondered if there was an opengl guru working on fixing this 
broken application ?. Or whether I should invest some time in learning 
more about the intricacies of wine and openg and NVidia !.. and fix it 
myself  ( my background is C and assembler (not Intel, but RT11 & Perkin 
Elmer)  ?

One of the users was asking about progress on fixing this app. I would 
like to respond back with some progress but suspect nobody is working on 
it :-(

Regards

Nick Law
*
Now where's that "Learn opengl/wine/graphics in 21 days" book ..*

WoW broken for wine 0.9.16 Nvidia cards

Nick wrote:
> Hi,
>
> Just a quick question, WoW ( World of Warcraft ) was broken  (for 
> Nvidia cards) with there latest software update. Is anybody working on 
> fixing Wow (with Nvidia Cards) ( working fine with ATI ).
>
> I just wondered if there was an opengl guru working on fixing this 
> broken application ?. Or whether I should invest some time in learning 
> more about the intricacies of wine and openg and NVidia !.. and fix it 
> myself  ( my background is C and assembler (not Intel, but RT11 & 
> Perkin Elmer)  ?
>
> One of the users was asking about progress on fixing this app. I would 
> like to respond back with some progress but suspect nobody is working 
> on it :-(
>
> Regards
>
> Nick Law
> *
> Now where's that "Learn opengl/wine/graphics in 21 days" book ..*

maybe I spoke too soon, a fix may have just become available ( we'll see 
after more tests ) :-)

[H. Verbeet]

> > > > CVS compile is broken on my machine:
> > > > I've got a patch for this, will send later.