On Dec 19, 2007 2:18 AM, Andrew Riedi <[EMAIL PROTECTED]> wrote:
> I have sent in a new patch with the same title to address the problems
> discussed in this thread. Thanks to all of the people who looked over my
> patch and discussed its possible problems. It should surely help debugging
> Wine
Peter Beutner wrote:
> btw., because you said "most of those gcc versions", is there
> a gcc version that is known to not work with wine (beside
> these copy protection issues)?
I couldn't name a specific one but I think when 4.0 versions started to
appear there were a few incidents of clearly
Another factor to consider is that individual distributions may work
while others do not. Vanilla gcc may work, but after Ubuntu/Suse/etc
apply their patches, this may not be the case.
-Austin
On Dec 20, 2007 8:11 PM, Peter Beutner <[EMAIL PROTECTED]> wrote:
> Rolf Kalbermatter schrieb:
> > Peter
Rolf Kalbermatter schrieb:
> Peter Beutner wrote:
>
>> just tested again with current git and it worked with every gcc version
>> I had at hand here: 4.2.2, 4.1.2, 4.0.4 and 3.4.6.
>
> And what did you test there?
That safedisc 2.x works. Wine successfully passes the statistical code analysis.
Peter Beutner wrote:
>just tested again with current git and it worked with every gcc version
>I had at hand here: 4.2.2, 4.1.2, 4.0.4 and 3.4.6.
And what did you test there? As far as I understood the issue, it's not that
Wine won't work at all (at least for most of those gcc versions). Those gc
Peter Beutner schrieb:
> John Klehm schrieb:
>> On Dec 18, 2007 9:43 AM, Peter Beutner <[EMAIL PROTECTED]> wrote:
>>
>>> As I recall this is not the only version that causes problems. Plus certain
>>> compiler
>>> flags have an influence as well. And as most distros ship gcc with a bunch
>>> of pa
I have sent in a new patch with the same title to address the problems
discussed in this thread. Thanks to all of the people who looked over my
patch and discussed its possible problems. It should surely help debugging
Wine in the future, especially if we decide to take advantage of the
http://wi
Scott Ritchie schrieb:
>
> Ughthis means that 4.2 for Ubuntu might NOT actually work, and that
> this is why System Shock 2 has been crashing at startup for me.
It usually didn't crash, just exits silently if the check fails, so this is
probably another issue. Anyway all this affects only sa
Jesse Allen wrote:
> On Dec 18, 2007 12:20 PM, Peter Beutner <[EMAIL PROTECTED]> wrote:
>> John Klehm schrieb:
>>> On Dec 18, 2007 9:43 AM, Peter Beutner <[EMAIL PROTECTED]> wrote:
>>>
As I recall this is not the only version that causes problems. Plus
certain compiler
flags have an
On Dec 18, 2007 12:20 PM, Peter Beutner <[EMAIL PROTECTED]> wrote:
> John Klehm schrieb:
> > On Dec 18, 2007 9:43 AM, Peter Beutner <[EMAIL PROTECTED]> wrote:
> >
> >> As I recall this is not the only version that causes problems. Plus
> >> certain compiler
> >> flags have an influence as well. An
John Klehm schrieb:
> On Dec 18, 2007 9:43 AM, Peter Beutner <[EMAIL PROTECTED]> wrote:
>
>> As I recall this is not the only version that causes problems. Plus certain
>> compiler
>> flags have an influence as well. And as most distros ship gcc with a bunch
>> of patches you probably can't even
On Dec 18, 2007 9:43 AM, Peter Beutner <[EMAIL PROTECTED]> wrote:
> As I recall this is not the only version that causes problems. Plus certain
> compiler
> flags have an influence as well. And as most distros ship gcc with a bunch
> of patches you probably can't even rely on the gcc version alon
Andrew Riedi schrieb:
> Sometimes Wine has optional features that users want to enable, but that
> require specific headers to compile. For bug reports, and the user IRC
> channel, it seemed a good idea to add an option to Wine to figure out
> what optional features have been compiled into Wine.
13 matches
Mail list logo
