RE: cvs update mystery

2004-10-09 Thread Michael DrĂ¼ing
Try "cvs update -dPR", that fixed a similar problem for me once (not in wine, though) (-d adds new directories, -P removes empty directories, -R recurses into subdirs) --Michael -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Kegel Sent: Saturday, Oc

'make check' hangs after crash in msvcrt/tests?

2004-10-09 Thread Dan Kegel
With this morning's cvs, 'make check' hangs after this point ... make[3]: Entering directory `/home/dank/winebuild/dlls/msvcrt/tests' ../../../../wine/tools/runtest -q -P wine -M msvcrt.dll -T ../../.. -p msvcrt_test.exe.so ../../../../wine/dlls/msvcrt/tests/cpp.c && touch cpp.ok fixme:msvcrt:__un

cvs update mystery

2004-10-09 Thread Dan Kegel
Last night I did a cvs update and built, and got a build failure dlls/amstream/amstream.c:40: parse error before "AM_Vtbl" Evidently cvs update failed to update the files in dlls/amstream, as it failed to pick up that part of this change: 2004-08-12 Alexandre Julliard <[EMAIL PROTECTED]>

Re: winsock: errs and fixmes, unimplemented socket level

2004-10-09 Thread Rein Klazes
On Sat, 9 Oct 2004 13:16:29 +0300 (EEST), you wrote: > Hi! > > When I start Space Empires IV, I get the following lines: > > fixme:winsock:convert_sockopt Unimplemented or unknown socket level > err:winsock:WS_setsockopt Invalid level (65407) or optname (128) > fixme:winsock:convert_sockopt Unim

tchar.h

2004-10-09 Thread Martin Fuchs
Hello, can anyone explain to me, what's the exact reason for the following error message in wine/include/tchar.h: #if defined(_UNICODE) || defined(_MBCS) #error You must use msvcrt when building in Unicode/MBCS mode #endif It disallows inclusion of this header file when using the _UNICODE defi

winsock: errs and fixmes, unimplemented socket level

2004-10-09 Thread Anssi Hannula
Hi! When I start Space Empires IV, I get the following lines: fixme:winsock:convert_sockopt Unimplemented or unknown socket level err:winsock:WS_setsockopt Invalid level (65407) or optname (128) fixme:winsock:convert_sockopt Unimplemented or unknown socket level err:winsock:WS_setsockopt Invalid