wine-devel January 2011

wine-devel@winehq.org

87 participants
238 discussions

Re: configure: Use -Wundef if supported by the compiler.
by Alexandre Julliard 04 Jan '11

04 Jan '11

Gerald Pfeifer <gerald(a)pfeifer.com> writes: > I verified this does not cause any warning on FreeBSD 8.1 test > builds, and all the tools like bison and flex in somewhat current > versions. It's broken here with bison 2.4.1: make[1]: Entering directory `/home/julliard/wine/wine/libs/wpp' gcc -m32 -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wundef -Wwrite-strings -Wpointer-arith -Werror -g -O2 -o ppy.tab.o ppy.tab.c ppy.tab.c:336:6: error: "YYENABLE_NLS" is not defined ppy.tab.c:910:6: error: "YYLTYPE_IS_TRIVIAL" is not defined make[1]: *** [ppy.tab.o] Error 1 -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: [2/9] kernel32: Improve parameter validation for WriteConsoleInputW. (try 3)
by Marvin 04 Jan '11

04 Jan '11

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=8097 Your paranoid android. === WINEBUILD (build) === Patch failed to apply Patch failed to apply

2 1

Re: [9/9] kernel32: Improve parameter validation for FillConsoleOutputAttribute. (try 3)
by Marvin 04 Jan '11

04 Jan '11

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=8104 Your paranoid android. === WINEBUILD (build) === Patch failed to apply Patch failed to apply

1 0

Re: [9/9] kernel32: Improve parameter validation for FillConsoleOutputAttribute. (try 3)
by Marvin 04 Jan '11

04 Jan '11

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=8104 Your paranoid android. === WINEBUILD (build) === Patch failed to apply Patch failed to apply

1 0

Re: [8/9] kernel32/tests: Add tests for FillConsoleOutputCharacterA. (try 3)
by Marvin 04 Jan '11

04 Jan '11

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=8103 Your paranoid android. === WINEBUILD (build) === Patch failed to apply Patch failed to apply

1 0

Re: [5/9] kernel32: Improve parameter validation for WriteConsoleOutputCharacterA. (try 3)
by Marvin 04 Jan '11

04 Jan '11

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=8100 Your paranoid android. === WINEBUILD (build) === Patch failed to apply Patch failed to apply

1 0

Re: [6/9] kernel32: Improve parameter validation for WriteConsoleOutputAttribute. (try 3)
by Marvin 04 Jan '11

04 Jan '11

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=8101 Your paranoid android. === WINEBUILD (build) === Patch failed to apply Patch failed to apply

1 0

Re: [3/9] kernel32: Improve parameter validation for WriteConsoleInputA. (try 3)
by Marvin 04 Jan '11

04 Jan '11

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=8098 Your paranoid android. === WINEBUILD (build) === Patch failed to apply Patch failed to apply

1 0

How to find out locking problem
by wylda＠volny.cz 03 Jan '11

03 Jan '11

Happy New Year! i notice, that since 1.3 i get quite offten locking issue. It looks like, that last OK version was 1.2-rc7. This problem happens in Bioshock on load/save, but i noticed that other users have same problem with games on the same game engine. Could someone help me, what should i do in this lockin-case as first, please? Thanks in advance! Regards W. ... fixme:thread:SetThreadIdealProcessor (0x734): stub err:ntdll:RtlpWaitForCriticalSection section 0x7deac200 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 001a, blocked by 0041, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x5486584 "?" wait timed out in thread 0045, blocked by 0044, retrying (60 sec)

2 1

Re: [PATCH] wine: pass $LDFLAGS also to $LDDLLFLAGS
by Alexandre Julliard 03 Jan '11

03 Jan '11

Marcus Meissner <marcus(a)jet.franken.de> writes: > This is helpful if you need to pass in special LDFLAGS, like -flto. LDFLAGS are already specified on the link command line, I don't think they should get hardcoded into winegcc. -- Alexandre Julliard julliard(a)winehq.org

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel January 2011