Le vendredi 02 avril 2010 10:40:07, Hans Leidekker a écrit :
> +MSI_RecordSetStringW( uirow, 2, mime->Extension->Extension );
I have a segfault on this line when executing GOG.com embedded Adobe Reader
installer (as of duke_nukem_manhattan_project.exe, SHA1SUM
98e6056472368867d302f5dc00c
Gerald Pfeifer wrote:
>From 722b0215c6e767d516844bdd492b479831f98557 Mon Sep 17 00:00:00 2001
From: Gerald Pfeifer
Date: Sat, 24 Apr 2010 12:13:33 +0200
Gerald:
Could you help us who are trying to match up what has changed by putting
the module name in braces like this:
[riched20]
som
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=1754
Your paranoid android.
> === W98SE (32 bit dib) ===
> dib.c:159: Test failed: Bitmap data not matching. [bTopDown=false,
> StretchDIBits(hMemDC, 103, 227, 663, 459, 33, 61, 663, 459, pBitmapData,
> &bmi, DIB_RGB_COLORS, SRCCOPY)]
[...]
> === WNT4WSSP6 (32 bit dib) ===
> dib.c:159: Test failed: Bitmap data not matching.
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=1753
Your paranoid android.
You caught me! I guess Ge will kill me.
Roderick
On Mon, Apr 26, 2010 at 9:05 PM, Paul Vriens wrote:
> On 04/26/2010 08:29 PM, Roderick Colenbrander wrote:
>>
>> This is actually patch 1/2 and the other 2/2. I should submit patches
>> in another way next time (either use --annotate, or edit them
Howdy all,
Wine has 5 Summer of Code students this year:
Alexander Soernes, Improving Wine's Internet Explorer GUI, mentored by
Maarten Lankhorst
David Hedberg, Implementing IExplorerBrowser, mentored by Eric Durbin
Mariusz Plucinski, Implementation of Windows Game Explorer equivalent,
mentored by
This is actually patch 1/2 and the other 2/2. I should submit patches
in another way next time (either use --annotate, or edit them or
whatever).
Roderick
Am 25.04.2010 18:52, schrieb Maarten Lankhorst:
> Hi AJ,
>
> I isolated and fixed the gcc bug, but it will take some time before the
> changes make it into wine stable. Should I add a testcase to configure
> to detect a broken version of gcc, and refuse to build wine64 if this is
> the case?
>
>
Detlef Riekenberg writes:
> @@ -55,8 +55,8 @@
> @ cdecl
> ?_set_se_translator@@YAP6AXIPAU_EXCEPTION_POINTERS@@@zp6a...@z@Z(ptr)
> msvcrt.?_set_se_translator@@YAP6AXIPAU_EXCEPTION_POINTERS@@@zp6a...@z@Z
> @ cdecl ?_sopen@@yahpbd...@z(str long long long) msvcrt._sopen
> @ stub ?_type_info_dtor
Hi Dmitry
I did.
But no one have actually done any of it.
And some threads actually talk about using assembler and some about
using open Watcom C compiler.
And (at that time) it seems that open Watcom had some problems.
So I went with the assembler way.
I feel that is the way that gives the m
Morten Rønne wrote:
> Since nobody at the moment can point to any other way of testing DOS, I
> have chosen to continue with the assembler path.
Looks like you haven't read the wine-devel thread I pointed you to.
--
Dmitry.
> From: Wolfram Sang
>
> while trying to deliver a testcase for Bug #14891 (Bitmaps with offset
> bits do not display correctly) I tried this patch:
>
> https://testbot.winehq.org/JobDetails.pl?Key=1740
>
> Two VMs reported the correct pixel as 0x instead of 0x00ff.
> (The truly failed
Hi Michael,
2010/4/26 Michael Stefaniuc :
> Maarten Lankhorst wrote:
>> ---
>> ;D
> As there is no fixed gcc out there I'd rather see configure warn here
> instead of aborting. We do want to make it easy for people to compile
> Wine64.
Any bug report would be useless on 64-bits with a broken gcc.
Hi Scott,
Yes we are looking at the possibility of pairing Phoromatic Tracker with
Wine, such as we have been doing already with our daily Linux kernel
benchmarks[1] and Ubuntu development packages[2].
Next week we should be hitting the first major milestone for the Windows
support with a nu
Do we want useless bug reports / wine test results? I agree that we
want as much people to compile wine64 though. Perhaps an acceptable
solution for now would be to mention that the current gcc is buggy and
let configure link to some easy to use script which can build a proper
compiler.
Roderick
Maarten Lankhorst wrote:
> ---
> ;D
As there is no fixed gcc out there I'd rather see configure warn here
instead of aborting. We do want to make it easy for people to compile
Wine64.
bye
michael
17 matches
Mail list logo
