Re: GetExitCodeProcess always returns 1

2006-03-24 Thread Dmitry Timoshkov
"Igor Sysoev" <[EMAIL PROTECTED]> wrote: The attached patch is the same patch but for Wine-0.9.10. I've tested it on FreeBSD 6.1. Please send it to wine-patches. If it's not included within next week or so I'd suggest to ask Alexandre directly what are his preferences in fixing this problem.

Re: GetExitCodeProcess always returns 1

2006-03-24 Thread Igor Sysoev
On Thu, 23 Mar 2006, Igor Sysoev wrote: 3 years ago I reported that on FreeBSD Wine-20030508's GetExitCodeProcess() always returns 1: http://www.winehq.org/hypermail/wine-devel/2003/06/0100.html This report included a small test case. It was fixed by patch: http://www.winehq.org/hypermail

Re: GetExitCodeProcess always returns 1

2006-03-23 Thread Dmitry Timoshkov
Hi Igor, "Igor Sysoev" <[EMAIL PROTECTED]> wrote: Maybe Alexandre would accept patches to add a todo_wine_freebsd {} to the test suite where there's things that are hard to fix? having todo_wine_xxx for each platform 'xxx' where a test is failing sounds not very elegant. It seems that I am

Re: GetExitCodeProcess always returns 1

2006-03-23 Thread Igor Sysoev
On Thu, 23 Mar 2006, Mike McCormack wrote: Igor Sysoev wrote: It seems the tests try to use my old .wine for Wine-20030508. I have renamed it and now I can run tests. Here are some failed tests (I run make -i test to ignore failures): ../../../tools/runtest -q -P wine -M kernel32.dll -T ../..

Re: GetExitCodeProcess always returns 1

2006-03-23 Thread Mike McCormack
Igor Sysoev wrote: It seems the tests try to use my old .wine for Wine-20030508. I have renamed it and now I can run tests. Here are some failed tests (I run make -i test to ignore failures): ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.e xe.so change.c && t

Re: GetExitCodeProcess always returns 1

2006-03-23 Thread Igor Sysoev
On Thu, 23 Mar 2006, Mike McCormack wrote: Igor Sysoev wrote: Should Wine be already installed before run these tests ? I've tried: make test ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so alloc.c && touch alloc.ok Warning: the specified Windows direct

Re: GetExitCodeProcess always returns 1

2006-03-23 Thread Mike McCormack
Igor Sysoev wrote: Should Wine be already installed before run these tests ? I've tried: make test ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so alloc.c && touch alloc.ok Warning: the specified Windows directory L"c:\\windows" is not accessible. Warnin

Re: GetExitCodeProcess always returns 1

2006-03-23 Thread Igor Sysoev
On Thu, 23 Mar 2006, Mike McCormack wrote: Igor Sysoev wrote: Well, but then I could not build Wine port under FreeBSD: as I understand the port runs something like ./configure && make depend && make && make install But I have built and installed Wine successfully. Sorry, misunderstood you.

Re: GetExitCodeProcess always returns 1

2006-03-22 Thread Mike McCormack
Igor Sysoev wrote: Well, but then I could not build Wine port under FreeBSD: as I understand the port runs something like ./configure && make depend && make && make install But I have built and installed Wine successfully. Sorry, misunderstood you. The tests don't run on every build, you ha

Re: GetExitCodeProcess always returns 1

2006-03-22 Thread Igor Sysoev
On Thu, 23 Mar 2006, Mike McCormack wrote: Igor Sysoev wrote: It seems that dlls/kernel/tests/process.c already has such test: test_ExitCode(). Does it run while usual build ? Yes, it is run after commits, so it's likely that it's only broken on FreeBSD. Well, but then I could not build W

Re: GetExitCodeProcess always returns 1

2006-03-22 Thread Mike McCormack
Igor Sysoev wrote: It seems that dlls/kernel/tests/process.c already has such test: test_ExitCode(). Does it run while usual build ? Yes, it is run after commits, so it's likely that it's only broken on FreeBSD. Mike

Re: GetExitCodeProcess always returns 1

2006-03-22 Thread Igor Sysoev
On Thu, 23 Mar 2006, Mike McCormack wrote: Igor Sysoev wrote: 3 years ago I reported that on FreeBSD Wine-20030508's GetExitCodeProcess() always returns 1: http://www.winehq.org/hypermail/wine-devel/2003/06/0100.html This report included a small test case. It was fixed by patch:

Re: GetExitCodeProcess always returns 1

2006-03-22 Thread Mike McCormack
Igor Sysoev wrote: 3 years ago I reported that on FreeBSD Wine-20030508's GetExitCodeProcess() always returns 1: http://www.winehq.org/hypermail/wine-devel/2003/06/0100.html This report included a small test case. It was fixed by patch: http://www.winehq.org/hypermail/wine-devel/2003/06

GetExitCodeProcess always returns 1

2006-03-22 Thread Igor Sysoev
3 years ago I reported that on FreeBSD Wine-20030508's GetExitCodeProcess() always returns 1: http://www.winehq.org/hypermail/wine-devel/2003/06/0100.html This report included a small test case. It was fixed by patch: http://www.winehq.org/hypermail/wine-devel/2003/06/0381.html and I use

Re: GetExitCodeProcess always returns 1

2005-05-05 Thread Dmitry Timoshkov
Hi Igor, sorry for the late response. "Igor Sysoev" <[EMAIL PROTECTED]> wrote: > 2 years ago I reported that on FreeBSD Wine-20030508's GetExitCodeProcess() > always returns 1: > http://www.winehq.org/hypermail/wine-devel/2003/06/0100.html > > It was fix

GetExitCodeProcess always returns 1

2005-03-31 Thread Igor Sysoev
2 years ago I reported that on FreeBSD Wine-20030508's GetExitCodeProcess() always returns 1: http://www.winehq.org/hypermail/wine-devel/2003/06/0100.html It was fixed by patch: http://www.winehq.org/hypermail/wine-devel/2003/06/0381.html and I used the patched Wine-20030508 all the time t