Re: Make test fails on pristine CVS checkout

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
Hi,
Following the discussion in Wineconf, I'm forwarding test failures to 
the list.

Methodology - Debian SID. I did apt-get build-dep wine (install most 
wine dependencies), and checked out a pristine CVS. ./configure (no 
parameters), make depend, make.
Next problem:
make[3]: Entering directory `/home/sun/sources/wine/dlls/oleaut32/tests'
../../../tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p 
oleaut32_test.exe.so olefont.c  touch olefont.ok
../../../tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p 
oleaut32_test.exe.so safearray.c  touch safearray.ok
../../../tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p 
oleaut32_test.exe.so typelib.c  touch typelib.ok
fixme:ole:LoadTypeLibEx Wanted to load Lolepro32.dll as typelib, but 
file was not found.
typelib.c:39: Test failed: Could not load type library

**
You must copy a 'stdole32.tlb' file to your Windows\System directory!
You can get one from a Windows installation, or look for the DCOM95 
package
on the Microsoft Download Pages.
**
fixme:ole:LoadTypeLibEx Wanted to load Lstdole32.tlb as typelib, but 
file was not found.
typelib.c:39: Test failed: Could not load type library
make[3]: *** [typelib.ok] Error 2
make[3]: Leaving directory `/home/sun/sources/wine/dlls/oleaut32/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/oleaut32'
make[1]: *** [oleaut32/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2
It seems to me there is no reason to halt the tests over this one.
 Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test fails on pristine CVS checkout

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
Hi,
Following the discussion in Wineconf, I'm forwarding test failures to 
the list.

Methodology - Debian SID. I did apt-get build-dep wine (install most 
wine dependencies), and checked out a pristine CVS. ./configure (no 
parameters), make depend, make.

Next I deleted the ~/.wine directory, and ran make test.
Here's another one.
make[3]: Entering directory `/home/sun/sources/wine/dlls/oleaut32/tests'
../../../tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p 
oleaut32_test.exe.so typelib.c  touch typelib.ok
fixme:ole:LoadTypeLibEx Wanted to load Lolepro32.dll as typelib, but 
file was not found.
typelib.c:39: Test failed: Could not load type library
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
make[3]: *** [typelib.ok] Error 1
make[3]: Leaving directory `/home/sun/sources/wine/dlls/oleaut32/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/oleaut32'
make[1]: *** [oleaut32/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2
Copying olepro32.dll from a native windows solved that one, but I think 
the tests should pass on pristine.

 Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test fails on pristine CVS checkout

2005-04-30 Thread Shachar Shemesh
make[3]: Entering directory `/home/sun/sources/wine/dlls/user/tests'
../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p 
user32_test.exe.so msg.c  touch msg.ok
err:mdi:get_client_info client 0x9009c belongs to other process
msg.c:788: Test failed: WM_LBUTTONDOWN on a button: the msg 0x0007 was 
expected, but got msg 0x0005 instead
msg.c:788: Test failed: WM_LBUTTONDOWN on a button: the msg 0x0135 was 
expected, but got msg 0x030f instead
msg.c:788: Test failed: WM_LBUTTONDOWN on a button: the msg 0x00f3 was 
expected, but got msg 0x0046 instead
msg.c:788: Test failed: WM_LBUTTONDOWN on a button: the msg 0x0135 was 
expected, but got msg 0x001c instead
msg.c:810: Test failed: WM_LBUTTONDOWN on a button: the msg sequence 
is not complete: expected  - actual 0086
make[3]: *** [msg.ok] Error 5
make[3]: Leaving directory `/home/sun/sources/wine/dlls/user/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/user'
make[1]: *** [user/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2

This one seems like a strange failure. I'm not sure how that came about, 
or why it fails on my system and not on Alexandre's.

 Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Sorry about the noise (was: Make test fails on pristine CVS checkout)

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
Hi,
Following the discussion in Wineconf, I'm forwarding test failures to 
the list.

Methodology - Debian SID. I did apt-get build-dep wine (install most 
wine dependencies), and checked out a pristine CVS. ./configure (no 
parameters), make depend, make.

Next I deleted the ~/.wine directory, and ran make test.
Please ignore this thread, as it was ran on old Wine code. I'll repeat 
the experiment with latest CVS, and report.

Sorry about the noise.
 Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
The results, this time really from CVS tip:

This time:
make[3]: Entering directory `/home/sun/sources/wine/dlls/dsound/tests'
../../../tools/runtest -q -P wine -M dsound.dll -T ../../.. -p 
dsound_test.exe.so dsound.c  touch dsound.ok
err:wave:DSDB_MapBuffer Could not map sound device for direct access 
(Input/output error)
err:wave:DSDB_MapBuffer Use: HardwareAcceleration = Emulation in 
the [dsound] section of your config file.
fixme:ole:CoCreateInstance no instance created for interface 
{279afa83-4981-11ce-a521-0020af0be560} of class 
{47d4d946-62e8-11cf-93bc-44455354}, hres is 0x80004005
dsound.c:175: Test failed: CoCreateInstance(CLSID_DirectSound) failed: 
E_FAIL
fixme:ole:CoCreateInstance no instance created for interface 
{279afa83-4981-11ce-a521-0020af0be560} of class 
{47d4d946-62e8-11cf-93bc-44455354}, hres is 0x8878000a
dsound.c:184: Test failed: CoCreateInstance(CLSID_DirectSound) failed: 
DSERR_ALLOCATED
fixme:ole:CoCreateInstance no instance created for interface 
{279afa83-4981-11ce-a521-0020af0be560} of class 
{47d4d946-62e8-11cf-93bc-44455354}, hres is 0x8878000a
dsound.c:193: Test failed: CoCreateInstance(CLSID_DirectSound) failed: 
DSERR_ALLOCATED
fixme:ole:CoCreateInstance no instance created for interface 
{11ab3ec0-25ec-11d1-a4d8-00c04fc28aca} of class 
{47d4d946-62e8-11cf-93bc-44455354}, hres is 0x80004002
fixme:ole:CoCreateInstance no classfactory created for CLSID 
{11ab3ec0-25ec-11d1-a4d8-00c04fc28aca}, hres is 0x80040154
err:wave:DSDB_MapBuffer Could not map sound device for direct access 
(Input/output error)
err:wave:DSDB_MapBuffer Use: HardwareAcceleration = Emulation in 
the [dsound] section of your config file.
fixme:winmm:MMDRV_Exit Closing while ll-driver open
fixme:winmm:MMDRV_Exit Closing while ll-driver open
make[3]: *** [dsound.ok] Error 3
make[3]: Leaving directory `/home/sun/sources/wine/dlls/dsound/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/dsound'
make[1]: *** [dsound/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2
Seems to be a missing interface. I don't think the Emulation warning 
has anything to do with it, as some tests before it printed the same 
error, but passed.

 Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
The results, this time really from CVS tip:

make[3]: Entering directory `/home/sun/sources/wine/dlls/gdi/tests'
../../../tools/runtest -q -P wine -M gdi32.dll -T ../../.. -p 
gdi32_test.exe.so metafile.c  touch metafile.ok
metafile.c:468: Test failed: (0,0)-(1000,1000), expected 
(0,0)-(1819,6675)
metafile.c:468: Test failed: (0,0)-(1000,1000), expected 
(0,0)-(1819,6675)
fixme:dc:GdiIsMetaPrintDC (nil)
fixme:dc:GdiIsPlayMetafileDC (nil)
fixme:dc:GdiIsMetaPrintDC 0x18c
fixme:dc:GdiIsPlayMetafileDC 0x18c
fixme:dc:GdiIsMetaPrintDC 0x19c
fixme:dc:GdiIsPlayMetafileDC 0x19c
make[3]: *** [metafile.ok] Error 2
make[3]: Leaving directory `/home/sun/sources/wine/dlls/gdi/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/gdi'
make[1]: *** [gdi/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2
I'm not sure what is the cause of this one.
 Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
The results, this time really from CVS tip:

make[3]: Entering directory `/home/sun/sources/wine/dlls/kernel/tests'
../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p 
kernel32_test.exe.so file.c  touch file.ok
fixme:vxd:VXD_Open Unknown/unsupported VxD Lbogus.vxd. Try setting 
Windows version to 'nt40' or 'win31'.
epoll_ctl: Operation not permitted
file.c:1392: Test failed: ret = 1, error 12345678
make[3]: *** [file.ok] Error 1
make[3]: Leaving directory `/home/sun/sources/wine/dlls/kernel/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/kernel'
make[1]: *** [kernel/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2

--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
The results, this time really from CVS tip:

make[3]: Entering directory `/home/sun/sources/wine/dlls/ole32/tests'
../../../tools/runtest -q -P wine -M ole32.dll -T ../../.. -p 
ole32_test.exe.so stg_prop.c  touch stg_prop.ok
err:heap:HEAP_ValidateInUseArena Heap 401e: in-use arena 40218fc8 
next block has PREV_FREE flag
err:heap:HEAP_ValidateInUseArena Heap 401e: prev arena 40218f60 is 
not prev for in-use 40218fc8
err:heap:HEAP_ValidateInUseArena Heap 401e: prev arena 40218f60 is 
not prev for in-use 40218fc8
err:heap:HEAP_ValidateInUseArena Heap 401e: in-use arena 40218fe8 
next block has PREV_FREE flag
err:heap:HEAP_ValidateInUseArena Heap 401e: in-use arena 40218fe8 
next block has PREV_FREE flag
stg_prop.c:372: Test failed: Didn't get expected type or value for 
property
make[3]: *** [stg_prop.ok] Error 1
make[3]: Leaving directory `/home/sun/sources/wine/dlls/ole32/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/ole32'
make[1]: *** [ole32/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2

--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
The results, this time really from CVS tip:
  Shachar
../../../tools/runtest -q -P wine -M oleaut32.dll -T ../../.. -p 
oleaut32_test.exe.so typelib.c  touch typelib.ok
err:ole:TLB_ReadTypeLib Loading of typelib Lolepro32.dll failed with 
error 1812
typelib.c:39: Test failed: Could not load type library
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
make[3]: *** [typelib.ok] Error 1
make[3]: Leaving directory `/home/sun/sources/wine/dlls/oleaut32/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/oleaut32'
make[1]: *** [oleaut32/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2
Copying olepro32.dll from a windows solves this one.
  Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Shachar Shemesh
Shachar Shemesh wrote:
The results, this time really from CVS tip:

make[3]: Entering directory `/home/sun/sources/wine/dlls/user/tests'
../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p 
user32_test.exe.so win.c  touch win.ok
fixme:win:WIN_CreateWindowEx Parent is HWND_MESSAGE
win.c:2165: Test failed: wrong focus window (nil)
win.c:2173: Test failed: wrong focus window (nil)
win.c:2176: Test failed: no message available
win.c:2177: Test failed: hwnd (nil) message 0100
win.c:2203: Test failed: no message available
win.c:2204: Test failed: hwnd (nil) message 0100
win.c:2642: Test failed: wrong update region
win.c:2655: Test failed: wrong update region
win.c:2695: Test failed: wrong update region
win.c:2704: Test failed: wrong update region
win.c:2713: Test failed: wrong update region
win.c:2728: Test failed: wrong update region
make[3]: *** [win.ok] Error 12
make[3]: Leaving directory `/home/sun/sources/wine/dlls/user/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/user'
make[1]: *** [user/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2

--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Shachar Shemesh

make[3]: Entering directory `/home/sun/sources/wine/dlls/winmm/tests'
../../../tools/runtest -q -P wine -M winmm.dll -T ../../.. -p 
winmm_test.exe.so wave.c  touch wave.ok
wave.c:594: Test failed: The sound played for 1169 ms instead of 1000 ms
make[3]: *** [wave.ok] Error 1
make[3]: Leaving directory `/home/sun/sources/wine/dlls/winmm/tests'
make[2]: *** [tests/__test__] Error 2
make[2]: Leaving directory `/home/sun/sources/wine/dlls/winmm'
make[1]: *** [winmm/__test__] Error 2
make[1]: Leaving directory `/home/sun/sources/wine/dlls'
make: *** [dlls/__test__] Error 2

--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/



Re: Make test status - latest CVS

2005-04-30 Thread Robert Reif
Shachar Shemesh wrote:
make[3]: Entering directory `/home/sun/sources/wine/dlls/dsound/tests'
../../../tools/runtest -q -P wine -M dsound.dll -T ../../.. -p 
dsound_test.exe.so dsound.c  touch dsound.ok
err:wave:DSDB_MapBuffer Could not map sound device for direct access 
(Input/output error)
err:wave:DSDB_MapBuffer Use: HardwareAcceleration = Emulation in 
the [dsound] section of your config file.

Seems to be a missing interface. I don't think the Emulation warning 
has anything to do with it, as some tests before it printed the same 
error, but passed.

 Shachar
This is a bug in your OSS driver.  It says it is capable of doing mmap 
but it fails when tried. 

The work around is to do as the message states: disable hardware 
acceleration (mmap).

Running the test manually with WINEDEBUG=+wave might give more insight.



Re: Make test status - latest CVS

2005-04-30 Thread Robert Reif
Shachar Shemesh wrote:
The problem is that I'm not interested in this test. I just think 
that, off the shelf, tests should not fail. My opinion is that if this 
is not a problem with Wine, it shouldn't fail the test.
The issue from a test perspective is that wine fails differently
than windows under this situation.  Wine really does
initialization at CoCreateInstance and our Initialize
really does nothing.  Wine should fail at Initialize, not
CoCreateInstance. 

Moving initialization to Initialize will require some
restructuring of the code in dsound.dll.  I'll look into it
but won't promis any fixes real soon.



Bug 1536

2005-04-30 Thread Dustin Navea
Can someone take a look at http://bugs.winehq.org/show_bug.cgi?id=1536 
and help out the author?  He has posted a WINEDEBUG=+key,+keyboard log 
to the bug and I am unable to determine the problem.  There are a few 
other bugs referenced near the bottom with similar (but not the same) 
problems which need looking at as well.  Thanks.

Dustin


Re: DirectX 9 patches

2005-04-30 Thread Jesse Allen
On 4/29/05, Oliver Stieber [EMAIL PROTECTED] wrote:
 Hi,
 
 I've put an updated patch and some new screeshost on
 sourceforge for the time being
 http://directxwine.sourceforge.net/

The patch may not be fully synched.  I get a rejection in
dlls/wined3d/direct.x with the snapshots of yesterday's cvs and last
week's cvs.

Jesse




Re: Quicken/CreateCompatibleBitmap issue revisited

2005-04-30 Thread Carl Sopchak
Thanks for the input, Rein.  Allowing either a width or height of zero to fall 
through should result in a 1x1 monochrome bitmap (I haven't tested it, but 
did read through the code and it looks like that would be returned).

However, the other points that I made call into question the need for the 
check at all.  XP has no size limit to a bitmap, at least that's mentioned on 
MSDN.

Is the intention of this condition one of a sanity check?  If so, should it 
be modified or even removed?  Has this code been around long enough so that 
the check isn't needed?  (I.e., was it included for stability/wine bug 
checking purposes?)  Or, maybe changing it to check that BOTH are = 0x1, 
or maybe their product is = 0x1 [can we get that precision on all 
wine platforms?] would be reasonable?  Or, do we go with the 16Mb Win95 
limit?

Thoughts?

Carl

On Friday, April 29, 2005 02:13 pm, Rein Klazes wrote:
 On Fri, 29 Apr 2005 10:46:31 -0400, you wrote:
  This seems wrong to me on
  three counts: (1) MSDN states that if either width or height is zero, a
  1x1 monochrome bitmap is returned

 Indeed, what happens if you try this obvious patch:

 8=
== --- wine/dlls/gdi/bitmap.c 2005-04-14 10:50:50.0 +0200
 +++ mywine/dlls/gdi/bitmap.c 2005-04-29 20:04:37.0 +0200
 @@ -134,7 +134,7 @@ HBITMAP WINAPI CreateCompatibleBitmap( H

  TRACE((%p,%d,%d) = \n, hdc, width, height);

 -if ((width = 0x1) || (height = 0x1))
 +if ((height  width = 0x1) || (width  height = 0x1))
  {
  FIXME(got bad width %d or height %d, please look for reason\n,
width, height);
 8=
==

 Rein.



Re: DirectX 9 patches

2005-04-30 Thread Vincent Béron
Hi Jesse,

The failures you see are only whitespace changes.
Either make patch skip whitespace changes, or apply the following patch
to Olivier's patch prior to apply it to your tree.

Vincent
--- d3d9patch.2005-04-28-2.diff 2005-04-29 11:17:13.0 -0400
+++ d3d9patch.2005-04-30-1.diff 2005-04-30 13:11:47.0 -0400
@@ -15745,7 +15745,7 @@
 -  int nCfgs = 0;
 -  int it;
 -  HRESULT hr = D3DERR_NOTAVAILABLE;
--
+-  
 -  WineD3D_Context* ctx = WineD3D_CreateFakeGLContext();
 -  if (NULL != ctx) {
 -  cfgs = glXGetFBConfigs(ctx-display, DefaultScreen(ctx-display), 
nCfgs);
@@ -15763,7 +15763,7 @@
 -  return hr;
 -  }
 -}
--
+- 
 -return D3DERR_NOTAVAILABLE;
 +/* TODO: use the real context if it's available */
 +ctx = WineD3D_CreateFakeGLContext();
@@ -16016,7 +16016,7 @@
  
  IWineD3DImpl*This = (IWineD3DImpl *)iface;
  BOOL gotContext  = FALSE;
- GLintgl_tex_size = 0;
+ GLintgl_tex_size = 0;
  WineD3D_Context *fake_ctx = NULL;
 -D3DCAPS9*pCaps = (D3DCAPS9 *)pCapsIn;
  
@@ -28126,7 +28126,7 @@
 diff -X ignore -Nru clean/wine/dlls/x11drv/opengl.c 
patch/wine/dlls/x11drv/opengl.c
 --- clean/wine/dlls/x11drv/opengl.c2005-04-28 18:12:00.0 +0100
 +++ patch/wine/dlls/x11drv/opengl.c2005-04-28 23:45:23.0 +0100
-@@ -414,14 +414,19 @@
+@@ -456,14 +456,19 @@
  XVisualInfo *X11DRV_setup_opengl_visual( Display *display )
  {
  XVisualInfo *visual = NULL;


Re: DirectX 9 patches

2005-04-30 Thread Ivan Gyurdiev
On Sat, 2005-04-30 at 13:25 -0400, Vincent Bron wrote:
 Hi Jesse,
 
 The failures you see are only whitespace changes.
 Either make patch skip whitespace changes, or apply the following patch
 to Olivier's patch prior to apply it to your tree.

gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include
-D__WINESRC__   -D_REENTRANT -fPIC -Wall -pipe
-mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+
-Wpointer-arith  -g -O2 -o directx.o directx.c
directx.c:36: error: static declaration of DeviceMemory follows
non-static declaration
directx.c:35: error: previous declaration of DeviceMemory was here

-- 
Ivan Gyurdiev [EMAIL PROTECTED]
Cornell University




Re: DirectX 9 patches

2005-04-30 Thread Vincent Béron
Le sam 30/04/2005  16:21, Ivan Gyurdiev a crit :
 On Sat, 2005-04-30 at 13:25 -0400, Vincent Bron wrote:
  Hi Jesse,
  
  The failures you see are only whitespace changes.
  Either make patch skip whitespace changes, or apply the following patch
  to Olivier's patch prior to apply it to your tree.
 
 gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include
 -D__WINESRC__   -D_REENTRANT -fPIC -Wall -pipe
 -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+
 -Wpointer-arith  -g -O2 -o directx.o directx.c
 directx.c:36: error: static declaration of DeviceMemory follows
 non-static declaration
 directx.c:35: error: previous declaration of DeviceMemory was here

Olivier's patch is the one adding both the extern and static
declarations of DeviceMemory. He's the one to who ask questions.

Vincent





Re: DirectX 9 patches

2005-04-30 Thread Jesse Allen
On 4/29/05, Oliver Stieber [EMAIL PROTECTED] wrote:
 Hi,
 
 I've put an updated patch and some new screeshost on
 sourceforge for the time being
 http://directxwine.sourceforge.net/, I'm now at the
 point where I'm happy to stop fixing bugs in DirectX 9
 and start sending in more patches..
 
 Thanks for evertyone help and support.
 Oliver.
 
 Send instant messages to your online friends http://uk.messenger.yahoo.com
 
 

Oh... Star Wars Battlefront digressed.  It now hits 100% CPU with
black screen when starting.