September 2012 - Wine-Devel

Re: winhttp: disable TLSv1.1/1.2 by default

by Henri Verbeet

On 26 August 2012 18:56, André Hentschel <nerv(a)dawncrow.de> wrote: > It's for http://bugs.winehq.org/show_bug.cgi?id=30598 > So it has its reason > So assuming I don't feel like reading through various bug trackers to figure this out, what is the specific issue this patch is supposed to address?

Sept. 2, 2012

Re: [PATCH 3/3] hhctrl.ocx: Resize the window when HH_SET_WIN_TYPE is called (try 3, resend 2).

by Erich E. Hoover

On Sun, Sep 2, 2012 at 2:18 PM, Charles Davis <cdavis5x(a)gmail.com> wrote: >... > Er, uh, what patch? Bah, usually Google warns me when I do that! Thanks! Erich

Sept. 2, 2012

Re: [PATCH] secur32/schannel: diabled TLS1.1/1.2 by Default

by Henri Verbeet

On 2 September 2012 10:58, Hiroshi Miura <miurahr(a)linux.com> wrote: > > -Set TLS1.1/1.2 disabled by Default that is > same as Windows 7 default. > Aside from whether disabling TLS1.1+ is appropriate or not, or if this is the right implementation, this patch also add %COMPAT to the priority string, which wasn't there before.

Sept. 2, 2012

Re: [PATCH 3/3] hhctrl.ocx: Resize the window when HH_SET_WIN_TYPE is called (try 3, resend 2).

by Charles Davis

On Sep 2, 2012, at 11:23 AM, Erich E. Hoover wrote: > This patch adds the final feature to make the embedded help work > properly, allowing Elster to resize the HTML Help window whenever the > application window is resized. Without this feature the HTML Help > window would always remain at the same size as when the window was > first created. Er, uh, what patch? Chip

Sept. 2, 2012

Re: vcomp.dll, vcomp90.dll missing on testbot?

by Dan Kegel

On Wed, Aug 8, 2012 at 7:27 AM, Dan Kegel <dank(a)kegel.com> wrote: > Testing vcomp100 does work, but I shouldn't need to > do that until there's some vcomp100-specific code. > > msvcr90/tests just adds a manifest, and that works. Heh. It does add a manifest, but I don't think it works. See http://bugs.winehq.org/show_bug.cgi?id=31603 - Dan

Sept. 2, 2012

Re: Wine Gecko 1.8-beta1

by Vincent Povirk

> On related note, I seriously consider dropping debug builds and replace > them by unstripped release build or even just a separated package > containing only debug symbols for the release build. No one has complained about the debugging symbols in Wine Mono yet. They are included mostly because I don't know how to get rid of them, and it seems silly to put effort into that given the debug symbols have proven useful so far.

Sept. 2, 2012

Re: [PATCH] kernel32: add condition variables prototypes and tests (2nd try)

by Marcus Meissner

On Sun, Sep 02, 2012 at 11:40:52PM +0900, Dmitry Timoshkov wrote: > Marcus Meissner <meissner(a)suse.de> wrote: > > > + if (!pInitializeConditionVariable) { > > + skip("no condition variable support.\n"); > > + return; > > + } > > Probably this should be a win_slip(). The function exists only since Windows 7/Vista (not XP) and is not yet in Wine (and might take a while, as my time is limited currently and my knowledge of this specific function same). So I think "skip" is currently the right thing ;) > > + /* fprintf(stderr,"produced %d, c1 %d, c2 %d\n", totalproduced, cnt1, cnt2); */ > > + > > + /* The sleeps of the producer or consumer should not go above 10000, otherwise > > + * the implementation does not sleep correctly. */ > > + > > + /* fprintf(stderr,"producer sleep %d, consumer sleep %d\n", condvar_producer_sleepcnt, condvar_consumer_sleepcnt); */ > > There is trace() for debug output, it's shorter and more convenient IMHO. True, I could do that, but its not relevant for the test as-is. Ciao, Marcus

Sept. 2, 2012

Re: [PATCH] kernel32: add condition variables prototypes and tests (2nd try)

by Vincent Povirk

>> Probably this should be a win_slip(). > > The function exists only since Windows 7/Vista (not XP) and is not yet > in Wine (and might take a while, as my time is limited currently > and my knowledge of this specific function same). > > So I think "skip" is currently the right thing ;) I think a "todo_wine win_skip" is appropriate for cases where Wine should have an implementation but doesn't yet.

Sept. 2, 2012

Re: [PATCH] kernel32: add condition variables prototypes and tests (2nd try)

by Dmitry Timoshkov

Marcus Meissner <meissner(a)suse.de> wrote: > + if (!pInitializeConditionVariable) { > + skip("no condition variable support.\n"); > + return; > + } Probably this should be a win_slip(). > + /* fprintf(stderr,"produced %d, c1 %d, c2 %d\n", totalproduced, cnt1, cnt2); */ > + > + /* The sleeps of the producer or consumer should not go above 10000, otherwise > + * the implementation does not sleep correctly. */ > + > + /* fprintf(stderr,"producer sleep %d, consumer sleep %d\n", condvar_producer_sleepcnt, condvar_consumer_sleepcnt); */ There is trace() for debug output, it's shorter and more convenient IMHO. -- Dmitry.

Sept. 2, 2012

Re: [PATCH] kernel32: add condition variables prototypes and tests

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 http://testbot.winehq.org/JobDetails.pl?Key=21332 Your paranoid android. === WINEBUILD (build) === Make failed

Sept. 2, 2012