+ /* reset to non-blocking behaviour */
+ fcntl(ret, F_SETFL, 0);
Shouldn't that read "reset to blocking behaviour" then?
--Juan
We have the perfect Group for you. Check out the handy changes to Yahoo! Group
Markus Amsler <[EMAIL PROTECTED]> writes:
> This fixes bug http://bugs.winehq.org/show_bug.cgi?id=6286
> ---
> programs/cmd/builtins.c | 22 ++
> 1 files changed, 22 insertions(+), 0 deletions(-)
> diff --git a/programs/cmd/builtins.c b/programs/cmd/builtins.c
> index 3329a0
On 10/31/06, Paul Vriens <[EMAIL PROTECTED]> wrote:
Hi,
most likely lstrcat was intended. I haven't checked why this lead to errors on
Windows and not on Wine.
It works in XP, at least, because you don't have to specify a full
pathname to the INF file. The test that shows that is just a coup
It says that wine is compiled with the:
./configure CFLAGS=-fno-stack-protector
So the bug shud not apply, also i have been installing binaries for
other distribution (debian binaries) also from winehq own ubuntu rep.
I think the problem is deeper in wine.
/Jimmy
sön 2006-10-29 klockan 13:09
Hi,
I have a problem displaying rotated text in Wine where the
rotation under Windows is counterclockwise, but the rotation
in Wine is clockwise.
The patch I came up with rotates the text in the right direction,
but the individual characters are still rotated in the wrong
direction.
The attached W
Pierre d'Herbemont <[EMAIL PROTECTED]> writes:
> 2) Launch a 'carbon' thread which will run the carbon run loop (which
> does not poll), and writes to a fd as soon as it receive events.
>
> I think 2) may be preferred but to have a separate thread that watch
> event and an other that act on the UI
Andrew Talbot <[EMAIL PROTECTED]> writes:
> @@ -1779,16 +1779,17 @@
>
> if (!lprect)
> flags &= ~ETO_CLIPPED;
> -
> +
> +reordered_str = HeapAlloc(GetProcessHeap(), 0, count * sizeof(WCHAR));
> +lstrcpynW(reordered_str, str, count);
The input string is not necessar
On Sat, 28 Oct 2006, martin pilka wrote:
> > Actually the shlfolder test seems to succeed on your machine and
> > it is the shlexec and shlfileop tests that are failing (and are working
> > for me).
> > Are you using a freshly generated ~/.wine directory?
>
> Before each "make test", ~/.wine di
