http://bugs.winehq.org/show_bug.cgi?id=33351
Bug #: 33351 Summary: Wine-15.27 GCC-4.8 x86_64 compilation issues: [-Wformat=] [-Wint-to-pointer-cast] errors / wine64 is somewhat broken (ie: winecfg crashes in 64bit prefix). Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: triplesquarednine@gmail.com Classification: Unclassified
Created attachment 44117 --> http://bugs.winehq.org/attachment.cgi?id=44117 wine64 gcc-4.8 errors: [-Wformat=] [-Wint-to-pointer-cast]
Using GCC-4.8.0(release) when compiling wine(64) highlights some errors in Wine's code... Areas affected; ntdll(signal_x86_64.c), jscript(string.c), oleaut32(tmarshal.c) and setupapi(devinst.c) ...
I've attached snippets of all of the errors in compilation (affecting above files), rather than including the full log, for convenience.
winecfg now crashes on my machine/ 64bit prefix(compiled with gcc-4.8), while with my old package (compiled with gcc-4.7.3), wine64 works as expected - so i have downgraded for now.
I won't bother with crash log from winecfg ~ because GCC has already pointed out the issue, i think.
cheerz
http://bugs.winehq.org/show_bug.cgi?id=33351
jordan triplesquarednine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win64
http://bugs.winehq.org/show_bug.cgi?id=33351
jordan triplesquarednine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |triplesquarednine@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=33351
jordan triplesquarednine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Wine-15.27 GCC-4.8 x86_64 |Wine-1.5.27 GCC-4.8 x86_64 |compilation issues: |compilation issues: |[-Wformat=] |[-Wformat=] |[-Wint-to-pointer-cast] |[-Wint-to-pointer-cast] |errors / wine64 is somewhat |errors/warning -> wine64 is |broken (ie: winecfg crashes |somewhat broken (ie: |in 64bit prefix). |winecfg crashes in 64bit | |prefix).
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #1 from jordan triplesquarednine@gmail.com 2013-04-07 21:39:18 CDT --- To add (since i didn't specify).
Archlinux 64bit (multilib) system AMD Phenom II 965 X4 / 8gig RAM kernel 3.8.4-rt2-1-l-pa #1 SMP PREEMPT RT x86_64 GNU/Linux gcc version 4.8.0 (GCC) (gcc-multilib) glibc 2.17
I also just noticed i have wine-1.5.21 sources, so i decided to check them over and i am getting some of the same errors. ( i don't recall seeing these before, pre-gcc-4.8 ).
thanks
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #2 from jordan triplesquarednine@gmail.com 2013-04-07 23:57:50 CDT --- To add (since i didn't specify).
Archlinux 64bit (multilib) system AMD Phenom II 965 X4 / 8gig RAM kernel 3.8.4-rt2-1-l-pa #1 SMP PREEMPT RT x86_64 GNU/Linux gcc version 4.8.0 (GCC) (gcc-multilib) glibc 2.17
I also just noticed i have wine-1.5.21 sources, so i decided to check them over and i am getting some of the same errors. ( i don't recall seeing these before, pre-gcc-4.8 ).
thanks
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #3 from Alexandre Julliard julliard@winehq.org 2013-04-08 03:54:42 CDT --- These are known issues that happen with older gcc too. If you get a winecfg crash it has nothing to do with these warnings.
http://bugs.winehq.org/show_bug.cgi?id=33351
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #4 from jordan triplesquarednine@gmail.com 2013-04-08 18:16:43 CDT --- Created attachment 44123 --> http://bugs.winehq.org/attachment.cgi?id=44123 winefcg-old-prefix-commandline
winecfg failing on old prefix
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #5 from jordan triplesquarednine@gmail.com 2013-04-08 18:18:49 CDT --- Created attachment 44124 --> http://bugs.winehq.org/attachment.cgi?id=44124 winecfg-fail-backtrace
backtrace from winecfg failing in 64bit prefix
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #6 from jordan triplesquarednine@gmail.com 2013-04-08 18:21:18 CDT --- @Alexandre
Regardless of whether or not if winecfg is failing because of this, these warnings/errors could lead to undesired behavior on x86_64, right?
Well, i am not sure why wine64 seems to be screwed on my system with gcc-4.8.0 (?)
I've attached 2 files one is the saved output from wine, the other the commandline to go with it. (for an existing wine prefix).
Next, i tried with a fresh wine-prefix (i'll paste here, since it is very short);
env WINEPREFIX=~/wine64 winecfg wine: created the configuration directory '/home/ninez/wine64' err:process:start_wineboot failed to start wineboot, err 1359 err:winecfg:WinMain failed to restart 64-bit L"C:\windows\system32\winecfg.exe", err 1359
Wine64 doesn't seem to be working as expected. So i thought the errors/warnings in my orignal post, may have been the cause. any ideas?
I'm glad at least i have packages/binaries for wine kicking around, otherwise wine would potentially be buggered.
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #7 from jordan triplesquarednine@gmail.com 2013-04-09 18:57:03 CDT --- Okay,
after some googling, it turns out Wine + gcc-4.8.0 equals problems;
http://bugs.winehq.org/show_bug.cgi?id=33307 http://forum.winehq.org/viewtopic.php?f=8&t=18631&sid=1a2cc4d34dba19...
on the first link the OP says setting optimization to -0O fixes (or at least allows wine64 to run ~ so i guess i will try that, then.
I will report back.
anyway, I think wine-devs should probably checkout GCC-4.8.0 as it is causing breakage on Wine.
cheerz
http://bugs.winehq.org/show_bug.cgi?id=33351
--- Comment #8 from jordan triplesquarednine@gmail.com 2013-04-09 22:18:47 CDT --- So, the bug report i linked to, does allow wine64 to work - but obviously, that isn't a permanent solution.
so these errors/warnings in my report aren't the cause of breakage on gcc-4.8.0 - but there is breakage with wine64 for sure.
i had thought maybe signal_x86_64.c throwing warnings was linked to the problem, but maybe not (?).
http://bugs.winehq.org/show_bug.cgi?id=33351
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2013-04-10 03:59:12 CDT --- Duplicate.
*** This bug has been marked as a duplicate of bug 33307 ***
http://bugs.winehq.org/show_bug.cgi?id=33351
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv@dawncrow.de
--- Comment #10 from André H. nerv@dawncrow.de 2013-04-13 16:27:39 CDT --- closing
http://bugs.winehq.org/show_bug.cgi?id=33351
sxe sxxe@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sxxe@gmx.de