Re: Segmentation Fault in wine cvs after 0.9

2005-11-07 Thread wino
On Mon, 07 Nov 2005 14:17:13 +0100, Christoph Frick <[EMAIL PROTECTED]> wrote: something is fishy in wine and at least its good to talk about it... and prevent this in the future. quite so, I think this got sorted pretty quickly by Rob so the patch should get into cvs to solve the anomoly.

Re: Segmentation Fault in wine cvs after 0.9

2005-11-07 Thread Christoph Frick
On Mon, Nov 07, 2005 at 12:31:37PM +0100, [EMAIL PROTECTED] wrote: > >oh well and btw: gcc 4.0.2.pre (or so) is my compiler. > come on fellas! now you're using unstable , pre-release compilers. > please dont waste time here. There enough true disfunctionality in Wine > that needs to be tracked d

Re: Segmentation Fault in wine cvs after 0.9

2005-11-07 Thread wino
On Mon, 07 Nov 2005 10:25:17 +0100, Christoph Frick <[EMAIL PROTECTED]> wrote: oh well and btw: gcc 4.0.2.pre (or so) is my compiler. come on fellas! now you're using unstable , pre-release compilers. please dont waste time here. There enough true disfunctionality in Wine that needs to b

Re: Segmentation Fault in wine cvs after 0.9

2005-11-07 Thread Christoph Frick
On Sun, Nov 06, 2005 at 05:29:02AM +0100, zhilla wrote: > before submitting this as bug, some advice please... > on slackware 10.2 (gcc 3.3.6) i compile wine cvs, and it has worked so > far. last version working is around or exactly 0.9. > now, it compiles/installs fine, but any program, includin

Re: Segmentation Fault in wine cvs after 0.9

2005-11-07 Thread Mike McCormack
Peter Beutner wrote: Besides there is nowhere stated that there are only certain supported compiler flags which you should use. Correct. Using any compiler flags other than what configure adds by default is unsupported, untested and unreliable. Even seemingly harmless flags such as "-Wall

Re: Segmentation Fault in wine cvs after 0.9

2005-11-07 Thread Marcus Meissner
On Sun, Nov 06, 2005 at 11:39:44PM +0100, Peter Beutner wrote: > Mike McCormack schrieb: > > zhilla wrote: > >> http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are > >> safe cflags, and it worked until couple days ago, then something is > >> definetly wrong, right? > > > > This is

Re: Segmentation Fault in wine cvs after 0.9

2005-11-06 Thread Peter Beutner
Mike McCormack schrieb: > Peter Beutner wrote: >> And it's not like -fomit-frame-pointer is such a high-risky >> optimization flag. >> Instead it is in general safe to use for 90% of applications out there > > If it fails for 10% of applications out there, then it's *not* safe! The question is how

Re: Segmentation Fault in wine cvs after 0.9

2005-11-06 Thread Mike McCormack
Peter Beutner wrote: And it's not like -fomit-frame-pointer is such a high-risky optimization flag. Instead it is in general safe to use for 90% of applications out there If it fails for 10% of applications out there, then it's *not* safe! (it basicly only prevents that you get some useful d

Re: Segmentation Fault in wine cvs after 0.9

2005-11-06 Thread Peter Beutner
Mike McCormack schrieb: > zhilla wrote: >> http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are >> safe cflags, and it worked until couple days ago, then something is >> definetly wrong, right? > > This is the wrong type of question for wine-devel, and better asked in > Gentoo foru

Re: Segmentation Fault in wine cvs after 0.9

2005-11-06 Thread wino
On Sun, 06 Nov 2005 19:11:26 +0100, <[EMAIL PROTECTED]> wrote: On Sun, 06 Nov 2005 05:29:02 +0100, zhilla <[EMAIL PROTECTED]> wrote: before submitting this as bug, some advice please... well if you have to pretend your Athlon-xp is a 486 to get wine to work I would say there's a problem th

Re: Segmentation Fault in wine cvs after 0.9

2005-11-06 Thread wino
On Sun, 06 Nov 2005 05:29:02 +0100, zhilla <[EMAIL PROTECTED]> wrote: before submitting this as bug, some advice please... on slackware 10.2 (gcc 3.3.6) i compile wine cvs, and it has worked so far. last version working is around or exactly 0.9. now, it compiles/installs fine, but any program,

Re: Segmentation Fault in wine cvs after 0.9

2005-11-06 Thread Mike McCormack
zhilla wrote: why it is wrong? developers are much more likely to know about compiler flags than users, and gentooers probably use much more bleeding edge version of gcc anyway The way developers recommend compiling Wine is explained in the README file. If you want our help, please try ou

Re: Segmentation Fault in wine cvs after 0.9

2005-11-06 Thread zhilla
Mike McCormack wrote: http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are safe cflags, and it worked until couple days ago, then something is definetly wrong, right? This is the wrong type of question for wine-devel, and better asked in Gentoo forums or wine-users. why it is

Re: Segmentation Fault in wine cvs after 0.9

2005-11-05 Thread Mike McCormack
zhilla wrote: http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are safe cflags, and it worked until couple days ago, then something is definetly wrong, right? This is the wrong type of question for wine-devel, and better asked in Gentoo forums or wine-users. Mike

Re: Segmentation Fault in wine cvs after 0.9

2005-11-05 Thread Dmitry Timoshkov
"zhilla" <[EMAIL PROTECTED]> wrote: > then, changed processor optimizations to much more conservative > "-O2 -march=i486 -mcpu=i686" > and it it works like a charm. > athlon-xp optimizatins used in the first place are from > http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are >

Segmentation Fault in wine cvs after 0.9

2005-11-05 Thread zhilla
before submitting this as bug, some advice please... on slackware 10.2 (gcc 3.3.6) i compile wine cvs, and it has worked so far. last version working is around or exactly 0.9. now, it compiles/installs fine, but any program, including starting just "wine", "notepad" or anything else, ends up qui