On Sunday 30 November 2008 00:52:57 Martin Storsjö wrote:
> poll can't handle terminal devices on Darwin, since Tiger. See the
> following discussion:
> http://lists.apple.com/archives/Darwin-dev/2006/Apr/msg00066.html
There's reasons we switched from select to poll. You can't just switch back to
Vincent Povirk wrote:
>> --- keyboard.old2008-11-27 16:53:15.0 +0100
>> +++ keyboard.c2008-11-26 21:19:01.0 +0100
All patches have to be generated from the top of the source tree (if you not
using git). This patch is invalid.
Vitaliy
I don't think "lpBuffer[nSize - 1] = 0;" is safe to remove. If nSize
is too small, the resulting string may not be NULL-terminated.
Patch-sending guidelines are at http://www.winehq.org/site/sending_patches.
Your patch is more likely to be committed if you write a conformance
test (although it ma
2008/11/30 Adam Petaccia <[EMAIL PROTECTED]>:
> Maarten, could you look at http://bugs.winehq.org/show_bug.cgi?id=16297
> as you're the author of 717df5b2972b3cb998ca5a43279ae2283b117eaa? I
> tried adding you as CC but bugzilla complained.
Hi,
You may be interested in http://bugs.winehq.org/show_
Maarten, could you look at http://bugs.winehq.org/show_bug.cgi?id=16297
as you're the author of 717df5b2972b3cb998ca5a43279ae2283b117eaa? I
tried adding you as CC but bugzilla complained.
Hi all,
I had managed to fix my selinux/wine/mono problem in fedora 10... it is
actually two issues, in fact:
1) fedora 10 ships some much stricter selinux policies (but make some exception
for wine).
2) I have kernel support for miscellaneous binary formats
enabled and have win32 PE registrat
On Sa, 2008-11-29 at 18:53 -0600, Austin English wrote:
> > gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
> -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
> -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits
> -Wpointer-arith -g -O2 -o serial.o serial.c
The problems with having the macros in the public headers are that they
won't work on x86 machines, and are not included in the public headers.
Therefore someone developing for another platform will have their code break
when using the native public headers or when porting the code to an x86
where
On Fri, Nov 28, 2008 at 4:51 AM, Michael Karcher
<[EMAIL PROTECTED]> wrote:
> Am Freitag, den 28.11.2008, 10:10 +0100 schrieb Michael Stefaniuc:
>> > Every year around this time, small elves creep down from the roof, and
>> > tamper with my computer while i am sleeping. They open all of my files
>>
"Susan Cragin" [EMAIL PROTECTED] wrote:
>I did the regression test. But how legitimate are the results if the problem
>is the new gcc that I downloaded recently,
>and not wine?
> gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease)
>
> [EMAIL PROTECTED]:~/wine$ git bisect bad
> Bisecting: 0 r
On Sun, Nov 30, 2008 at 10:24:56AM -0500, Susan Cragin wrote:
> I did the regression test. But how legitimate are the results if the problem
> is the new gcc that I downloaded recently, and not wine?
> gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease)
>
> [EMAIL PROTECTED]:~/wine$ git bise
Am Freitag, den 28.11.2008, 10:10 +0100 schrieb Michael Stefaniuc:
> > Every year around this time, small elves creep down from the roof, and
> > tamper with my computer while i am sleeping. They open all of my files
> > and fill them with whitespaces. You should see what they did to my
> > desktop
I did the regression test. But how legitimate are the results if the problem is
the new gcc that I downloaded recently, and not wine?
gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease)
[EMAIL PROTECTED]:~/wine$ git bisect bad
Bisecting: 0 revisions left to test after this
[0b7478a79fb0594da
Am Sonntag, den 30.11.2008, 07:42 -0500 schrieb Susan Cragin:
> Need the number of the current git because am doing regression on it,
> because it doesn't compile on my machine using my gcc.
Sorry, I don't really understand what you mean. If you mean the commit
ID of your tree, you just look into
Susan Cragin wrote:
> Need the number of the current git because am doing regression on it, because
> it doesn't compile on my machine using my gcc.
> gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease)
> (And BTW can the regression test page link to this page?)
> Thank you very much.
> Sus
Need the number of the current git because am doing regression on it, because
it doesn't compile on my machine using my gcc.
gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease)
(And BTW can the regression test page link to this page?)
Thank you very much.
Susan
16 matches
Mail list logo
