[PATCH] server: Use syscall(2) instead of inline assembly on Mac OS; too.
cdavis at mymail.mines.edu
Fri Oct 7 16:25:59 CDT 2011
On Oct 7, 2011, at 1:50 PM, Dan Kegel wrote:
> Probably a spurious failure
Yeah... especially considering that:
- That change only affects Mac OS X, and I haven't added my buildslave yet ;). (That file shouldn't even get built on non-Darwin.)
- Wine won't even build 64-bit on Mac OS yet (and might never).
> - I was running rpcrt4 tests on
> that machine, and they may both have wanted the same port number.
> Shame on me.
> On Fri, Oct 7, 2011 at 12:48 PM, Dan Kegel <dank at kegel.com> wrote:
>> Fails tests on x86_64?
>> On Fri, Oct 7, 2011 at 11:52 AM, <buildbot at kegel.com> wrote:
>>> This is an experimental automated build and test service.
>>> Please feel free to ignore this email while we work the kinks out.
>>> For more info about this message, see http://wiki.winehq.org/BuildBot
>>> The Buildbot has detected a failed build on builder runtests-default-x86_64 while building Wine.
>>> Full details are available at: http://buildbot.kegel.com/builders/runtests-default-x86_64/builds/35 (though maybe not for long, as I'm still reinstalling the buildbot periodically while experimenting)
>>> BUILD FAILED: failed shell_3
>>> alarum: failed command was ../../../wine rpcrt4_test.exe.so rpc.c
>>> fixme:rpc:RpcNetworkIsProtseqValidW Unknown protseq L"foo"
>>> err:rpc:rpcrt4_protseq_ncacn_ip_tcp_open_endpoint couldn't listen on port 4114
>>> rpc.c:238: Test failed: RpcServerUseProtseqEp failed (1740)
>>> fixme:rpc:RpcBindingInqAuthInfoExW authorization service not implemented
>>> make: *** [rpc.ok] Error 1
More information about the wine-devel