cvs build fails

[Christian Gmeiner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


make[2]: Entering directory
`/home/austriancoder/development/wine/dlls/wined3d'
../../tools/winegcc/winegcc -B../../tools/winebuild -shared
./wined3d.spec    basetexture.o cubetexture.o device.o directx.o
drawprim.o indexbuffer.o pixelshader.o query.o resource.o stateblock.o
surface.o swapchain.o texture.o utils.o vertexbuffer.o
vertexdeclaration.o vertexshader.o volume.o volumetexture.o
wined3d_main.o     -o wined3d.dll.so -L../../dlls -L../../dlls/user32
- -L../../dlls/gdi32 -L../../dlls/advapi32 -L../../dlls/kernel32 -luser32
- -lgdi32 -ladvapi32 -lkernel32  -L../../libs/wine -lwine -luuid   -lSM
- -lICE -lXxf86dga -lXxf86vm -lXext -lX11  -lGL -lGLU -L../../libs/port
- -lwine_port
device.o: In function `IWineD3DDeviceImpl_SetRenderState':
/home/austriancoder/development/wine/dlls/wined3d/device.c:3770:
undefined reference to `glStencilOpSeparate'
/home/austriancoder/development/wine/dlls/wined3d/device.c:3799:
undefined reference to `glStencilFuncSeparate'
collect2: ld gab 1 als Ende-Status zurück


- --
Christian Gmeiner - student of computer science

http://dxr3plugin.sf.net
http://itb04.ath.cx
http://javamill.ath.cx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEBGGdDwe2AbwGBA8RAik/AJ9KYo38XkVojj6klecVd7NzMsAUuACeIm7z
3gkx7axC0uKtlFbZm1wstVw=
=Z3Kf
-----END PGP SIGNATURE-----

[H. Verbeet]

On 28/02/06, Christian Gmeiner
<christian.gmeiner(a)students.fh-vorarlberg.ac.at> wrote:
> device.o: In function `IWineD3DDeviceImpl_SetRenderState':
> /home/austriancoder/development/wine/dlls/wined3d/device.c:3770:
> undefined reference to `glStencilOpSeparate'
> /home/austriancoder/development/wine/dlls/wined3d/device.c:3799:
> undefined reference to `glStencilFuncSeparate'
> collect2: ld gab 1 als Ende-Status zurück
> If that's with current CVS, it's probably this patch that broke it:
> http://source.winehq.org/git/?p=wine.git;a=commit;h=63585380a9a8caf4379d70b4...

You should probably ask its author to fix it...