On Mon, 12 Sep 2011, Octavian Voicu wrote:
> On Mon, Sep 12, 2011 at 12:22 AM, Francois Gouget wrote:
> > - assert(0 && "bad encoding in load_encoding_name");
> > + assert("bad encoding in load_encoding_name");
>
> Hello,
>
> assert() is a debug macro which generates some
Fails to compile on gcc-2.95 here:
visual.c: In function `enum_z_fmt':
visual.c:61: request for member `u1' in something not a structure or union
visual.c:61: request for member `u1' in something not a structure or union
make[1]: *** [visual.o] Error 1
make: *** [dlls/ddraw/tests] Error 2
--
Hi Frédéric,
fails a test here:
../../../tools/runtest -q -P wine -M cryptnet.dll -T ../../.. -p
cryptnet_test.exe.so cryptnet.c && touch cryptnet.ok
fixme:cryptnet:CryptGetObjectUrl unimplemented for 0
cryptnet.c:444: Test failed: Expected ERROR_FILE_NOT_FOUND or
ERROR_PATH_NOT_FOUND, got 123
-
On Mon, Sep 12, 2011 at 12:22 AM, Francois Gouget wrote:
> - assert(0 && "bad encoding in load_encoding_name");
> + assert("bad encoding in load_encoding_name");
Hello,
assert() is a debug macro which generates some code such that, during
runtime: if the argument is non-zer
On Sun, 11 Sep 2011, Alistair Leslie-Hughes wrote:
[...]
> > So what's going on?
> >
> I have taken my values from xmlparser.idl found in the the PocketPC SDK that
> is included with VS 2008.
I think that's the problem. Wine reimplements the Windows' Platform SDK
Win32 and Win64 APIs, not Window
On 09/11/2011 04:58 AM, Gerald Pfeifer wrote:
> On Thu, 8 Sep 2011, Alexandre Julliard wrote:
>> It's still wrong, the parameter is used inside the #ifdef.
>
> Fair enough! How about the patch below then? Tested with and
> without WANT_NEAR_INDICATION defined this time.
This is patch is ugly. Ju
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=14145
Your paranoid android
On Saturday 10 September 2011 21:56:26 Dan Kegel wrote:
> Might want to define the new form as ok2_ or something
> so we can defer changing the explicit uses of ok_().
I dislike the idea, it has the feeling of legacy cruft. Either way it is a
fairly minor point - the main change that needs debatin
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=14136
Your paranoid android
On Thu, 8 Sep 2011, Alexandre Julliard wrote:
> It's still wrong, the parameter is used inside the #ifdef.
Fair enough! How about the patch below then? Tested with and
without WANT_NEAR_INDICATION defined this time.
Or would you rather see a patch that remove WANT_NEAR_INDICATION
altogether?
G
10 matches
Mail list logo