On Sat, 25 Mar 2006, Eric Pouech wrote:
Igor Sysoev wrote:
On Thu, 23 Mar 2006, Eric Pouech wrote:
Igor Sysoev wrote:
When I try to run any program from Digital Mars C/C++ Compiler
http://www.digitalmars.com/download/freecompiler.html
under Wine 0.9.10 on FreeBSD 6.1, I always see the
On Thu, 23 Mar 2006, Igor Sysoev wrote:
When I try to link with ilink32.exe from C++ Builder Compiler and
Command Line Tools ( http://appdb.winehq.org/appview.php?versionId=1423 )
ilink32 hangs.
I saw comment on http://appdb.winehq.org/appview.php?versionId=1423
about changing
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
On Thu, 23 Mar 2006, Eric Pouech wrote:
Igor Sysoev wrote:
When I try to run any program from Digital Mars C/C++ Compiler
http://www.digitalmars.com/download/freecompiler.html
under Wine 0.9.10 on FreeBSD 6.1, I always see the error:
this works fine here (on Linux)... may be a freebsd issue
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
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 spec
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.
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
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:
When I try to link with ilink32.exe from C++ Builder Compiler and
Command Line Tools ( http://appdb.winehq.org/appview.php?versionId=1423 )
ilink32 hangs.
I saw comment on http://appdb.winehq.org/appview.php?versionId=1423
about changing ADDRESS_SPACE_LIMIT. Could be applied to 0.9.10 ?
Igor
Debug info Name (0 modules)
Threads:
process tid prio (all id:s are in hex)
0016 (D) C:\dmc\bin\dmc.exe
00170 <==
0008
00090
Igor Sysoev
http://sysoev.ru/en/
d the patched Wine-20030508 to run MSVC,
OpenWatcom C, and Borland C in a command line.
Recenty I build Wine-0.9.10 from ports on FreeBSD 6.1, but
GetExitCodeProcess() still always returns 1.
Igor Sysoev
http://sysoev.ru/en/
ms:
1) GetExitCodeProcess() always returns 1 on FreeBSD 5.3,
2) and wine could not run Digital Mars C/C++ Compiler.
Digital Mars C/C++ Compiler is could be downloaded here:
http://www.digitalmars.com/download/freecompiler.html
Igor Sysoev
http://sysoev.ru/en/
13 matches
Mail list logo
