I don't know about compiling, but there are several other reasons to
keep waiting, listed here:
http://forum.winehq.org/viewtopic.php?t=15802
Regards,
Daniel
2012/6/25, Erich E. Hoover :
> I know that for a while there were some packaging problems that meant that
> upgrading to 12.04 made compili
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=19550
Your paranoid android
On Mon, Jun 25, 2012 at 10:40 PM, Marvin wrote:
> 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://tes
Francois Gouget wrote:
> >
> > Do you think it's worth changing these?
>
> Not necessarily. The only thing I'd feel like changing would be to [...]
Alexandre Julliard wrote:
> Test failure messages are not supposed to be seen, if they are seen it's
> a bug. So it's not worth spending effort maki
2012/6/25 Erich E. Hoover :
> I know that for a while there were some packaging problems that meant that
> upgrading to 12.04 made compiling 32-bit Wine on a 64-bit PC extremely
> difficult. Is this still the case?
I've spent several hours on this over the past few days and rewrote
the wiki page
On Sun, 24 Jun 2012, Julian Rüger wrote:
[...]
> ok( !retval, "function result wrong! False expected\n");
> or
> ok( size == exact, "Parameter size wrong! %d expected got %d\n",
> exact, size);
>
>
> Do you think it's worth changing these?
Not necessarily. The only thing I'd feel
On Mon, Jun 25, 2012 at 11:21:33PM +0200, Hilko Bengen wrote:
> Hi,
>
> after the effort on the Debian wine packages has progressed to a point
> where it's likely that we'll release wheezy with a stable wine version
> that is not completely out of date, I'd like to take things a step
> further.
>
Hi,
after the effort on the Debian wine packages has progressed to a point
where it's likely that we'll release wheezy with a stable wine version
that is not completely out of date, I'd like to take things a step
further.
I recently spent some time looking at ways how we could build Debian
packag
André Hentschel wrote:
> Am 25.06.2012 19:29, schrieb Erich E. Hoover:
> You should wait until Scott Ritchie gives green light here. I blindly
> upgraded and it was a mess, so don't hurt yourself. I'm now back at 11.04 and
> that's pretty comfort, i also really dislike every non-gnome2 desktop, m
> I know that for a while there were some packaging problems that meant
> that upgrading to 12.04 made compiling 32-bit Wine on a 64-bit PC
> extremely difficult.
I was able to patch and build 32-bit wine on 64-bit 12.04, using a
debootstrap chroot:
https://help.ubuntu.com/community/Debootstr
Am 25.06.2012 19:29, schrieb Erich E. Hoover:
> I know that for a while there were some packaging problems that meant that
> upgrading to 12.04 made compiling 32-bit Wine on a 64-bit PC extremely
> difficult. Is this still the case? I'd like to upgrade to the new OS
> version, but I'm not will
I know that for a while there were some packaging problems that meant that
upgrading to 12.04 made compiling 32-bit Wine on a 64-bit PC extremely
difficult. Is this still the case? I'd like to upgrade to the new OS
version, but I'm not willing to sacrifice the ability to build Wine in
order to do
On Mon, Jun 25, 2012 at 1:22 AM, Chris Robinson wrote:
> On Sunday, June 24, 2012 10:42:11 PM Roderick Colenbrander wrote:
>> @@ -797,7 +797,7 @@ static void test_getprocaddress(HDC hdc)
>> /* Temporarily disable the context, so we can see that we can't
>> retrieve functions now. */ wglMakeCu
On 6/25/2012 14:30, Dmitry Timoshkov wrote:
+
+return hr == S_OK ? Ok : hresult_to_status(hr);
}
No need for special case for S_OK here.
On Sunday, June 24, 2012 10:42:11 PM Roderick Colenbrander wrote:
> @@ -797,7 +797,7 @@ static void test_getprocaddress(HDC hdc)
> /* Temporarily disable the context, so we can see that we can't
> retrieve functions now. */ wglMakeCurrent(hdc, NULL);
> func = wglGetProcAddress("glActiveTe
Julian Rüger writes:
> Hi Francois and list,
>
> [/nitpick-mode on]
> I'm preparing a patch to fix typos/spelling/grammar in
> dlls/winspool.drv/tests/info.c, where I stumbled across repeated
> messages like
>
> ok( !retval, "function result wrong! False expected\n");
> or
> ok( size == e
16 matches
Mail list logo
