October 2013 - Wine-Devel - list.winehq.org

Re: [00/11] msi/tests: Prepare action.c for the switch to -D__WINESRC__.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2775 Your paranoid android. === build (build) === Patch failed to apply

Oct. 15, 2013

Re: [10/11] msi/tests: Prepare msi.c for the switch to -D__WINESRC__.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2769 Your paranoid android. === wvista (32 bit msi) === The test timed out === w2008s64 (32 bit msi) === The test timed out === w7pro64 (32 bit msi) === Timeout === w2008s64 (64 bit msi) === Timeout === w7pro64 (64 bit msi) === Timeout

Oct. 15, 2013

Re: [11/11] msi/tests: Compile with -D__WINESRC__.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2770 Your paranoid android. === build (build) === Make failed

Oct. 15, 2013

Re: [04/11] msi/tests: Prepare install.c for the switch to -D__WINESRC__.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2763 Your paranoid android. === wxppro (32 bit install) === No test summary line found Failure running script in VM: network read timed out === wvista (32 bit install) === Timeout === w2008s64 (32 bit install) === Failure running script in VM: network read timed out === w7pro64 (32 bit install) === Timeout Failure running script in VM: timed out waiting for the child process === w864 (32 bit install) === install.c:2439: Test failed: Directory not created === w2008s64 (64 bit install) === Timeout

Oct. 15, 2013

Re: dlls/explorerframe: build tests with -D__WINESRC__

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=2750 Your paranoid android. === wvista (32 bit nstc) === nstc.c:1934: Test failed: Got event 7, count 0 nstc.c:1936: Test failed: Got event 4, count 0 nstc.c:1949: Test failed: Got event 4, count 0

Oct. 14, 2013

Re: wsock32: Add a fallback for inet_network.

by Alexandre Julliard

Huw Davies <huw(a)codeweavers.com> writes: > --- > dlls/wsock32/protocol.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) This doesn't build on MingW: protocol.o: In function `WSOCK32_inet_network(a)4': /home/julliard/wine/build/obj-pe32/dlls/wsock32/../../../wine/dlls/wsock32/protocol.c:55: undefined reference to `_inet_addr' /home/julliard/wine/build/obj-pe32/dlls/wsock32/../../../wine/dlls/wsock32/protocol.c:55: undefined reference to `_ntohl' collect2: ld returned 1 exit status winegcc: i686-w64-mingw32-gcc failed -- Alexandre Julliard julliard(a)winehq.org

Oct. 14, 2013

RE: Help / Mentoring

by Hugh McMaster

On Monday, 14 October 2013 9:50 PM, Ricardo Filipe wrote: >I'd be more than happy to help you review your patches, although I am no wineconsole expert, I believe I could help you get your changes into wine. >Contact me if no better offer comes around :) cheers Hello Ricardo, Thank you for your kind offer. I'll contact you via email. Hugh

Oct. 14, 2013

Re: Help / Mentoring

by Ricardo Filipe

Hello Hugh, I'd be more than happy to help you review your patches, although I am no wineconsole expert, I believe I could help you get your changes into wine. Contact me if no better offer comes around :) cheers 2013/10/11 Hugh McMaster <hugh.mcmaster(a)masterindexing.com>: > Can anyone help me on this? I do realize that wineconsole is only a minor focus of development. > > Hugh > > ------------------------------------------------- > > Hi everyone, > > I just wanted to know if anyone would mind helping/mentoring me with a few small patches. > > I am working primarily on wineconsole's screen buffer problems (to which I believe I have the solution), but am also looking at implementing some stub Win32 console functions found in dlls/kernel32. Obviously, my aim is to have these patches committed, as the changes will benefit the entire Wine community. > > I had initially thought of Eric Poeuch, a significant wineconsole developer, however he appears to be extremely busy. So I'm not sure who else to contact. > > If time is a consideration, please note that I won't be constantly contacting you to review patches or answer questions. > > Thank you, > > Hugh > >

Oct. 14, 2013

Re: Mono Update

by Ricardo Filipe

IMHO it is more than time. Mono has several release cycles of new features that we are not taking advantage of with wine-mono cheers 2013/10/14 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com>: > Hi, > > wine-mono hasn't been updated in nearly a year. Should it be time to > consider a new release? > > Thoughts. > > Best Regards > Alistair Leslie-Hughes > >

Oct. 14, 2013

Re: [PATCH] d3drm: added some freeing of memory in error paths (Coverity)

by Henri Verbeet

On 13 October 2013 11:13, Marcus Meissner <marcus(a)jet.franken.de> wrote: > 1104553 Resource leak > Fixing the memory leak is fine of course, but I think it would be better to handle the array initialization in d3drm_visual_array_create() etc. instead, so that those functions actually return an object that's properly initialized.

Oct. 14, 2013