Re: today's git does not compile
Nicely done! Thanks for taking the time to do the full-on gcc bug report with .i file. If at some point in the future you want to ascend to the next level of gcc bug reporting awesomeness, read up on delta debugging, an easy technique for automatically reducing the .i file to (nearly) the smallest possible input file that causes the crash. http://en.wikipedia.org/wiki/Delta_Debugging Or don't; it's an easy next step for the gcc professionals, given what you gave them. - Dan
re: today's git does not compile
https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/704633 Bug successfully updated and confirmed by a member of Ubuntu's testing team, so we're off to the races.
Re: today's git does not compile
On Wed, Jan 19, 2011 at 4:46 AM, Reece Dunn wrote: > You need to run it with the command line given in your output in the > directory where it was run. That is: > > cd /home/susan/wine/dlls/winex11.drv > > gcc -save-temps -m32 -c -I. -I. -I../../include -I../../include > -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing > -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits > -Wwrite-strings -Wpointer-arith -Wlogical-op -g -O2 -U_FORTIFY_SOURCE > -D_FORTIFY_SOURCE=0 -o pen.o pen.c Perhaps more simply, you can do cd ~/wine-git ./configure CFLAGS="-O2 -save-temps" make It should crash as usual, but this time you should see a pen.i file laying around next to pen.o. (Ignore the warnings about -pipe being ignored.) Sadly, because of the way Wine generates its makefiles, you can't just cd to dlls/winex11 yourself and do 'make pen.o', it won't get the -save-temps option. If you're not afraid of editing Makefiles, though, you can skip all the above and do cd ~/wine-git/dlls/winex11 vi Makefile (and change -pipe to -save-temps) rm -f pen.o make pen.o That's faster. - Dan
Re: today's git does not compile
On 19 January 2011 12:41, Susan Cragin wrote: > Dan, I can't work the -save-temps option. All three give me "no input files." > /wine-git$ gcc -save-temps > /wine-git$ gcc -save-temps=cwd (or =obj) > gcc: no input files You need to run it with the command line given in your output in the directory where it was run. That is: cd /home/susan/wine/dlls/winex11.drv gcc -save-temps -m32 -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits -Wwrite-strings -Wpointer-arith -Wlogical-op -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -o pen.o pen.c HTH, - Reece
re: today's git does not compile
>Try switching from -O2 to -O1 with > configure CFLAGS="-g -O1" >and rebuild. Does that help? Yes. That works. >Regardless of whether that gets you past the problem, >please file a bug in launchpad against gcc-4.5. >Ideally they'd want you to run with -save-temps and give >them a copy of pen.i. https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/704633 Here's the bug. I http://www.network-theory.co.uk/docs/gccintro/gccintro_36.html Dan, I can't work the -save-temps option. All three give me "no input files." /wine-git$ gcc -save-temps /wine-git$ gcc -save-temps=cwd (or =obj) gcc: no input files
Re: today's git does not compile
> It's not wine's fault, and you're not missing any dependencies; the >> new version of gcc is probably buggy, and the bug is triggered by >> something inside wine. > >If you've compiled Wine before and are re-using object files from an >old gcc it's possible that there is a conflict between the object >files from before and the object files with your new version of gcc. >So, you could try a "make clean" and then compile again. > >Erich Hoover >ehoo...@mines.edu I tried "make distclean" and also tried a new wine-git download... so far nothing. On with the flags test.
Re: today's git does not compile
On Tue, Jan 18, 2011 at 12:04 PM, Erich Hoover wrote: > On Tue, Jan 18, 2011 at 12:55 PM, Dan Kegel wrote: >> ... >> It's not wine's fault, and you're not missing any dependencies; the >> new version of gcc is probably buggy, and the bug is triggered by >> something inside wine. > > If you've compiled Wine before and are re-using object files from an > old gcc it's possible that there is a conflict between the object > files from before and the object files with your new version of gcc. > So, you could try a "make clean" and then compile again. While "make clean" is good advice in general, and Susan should do that before doing the -O1 rebuild, I have a feeling the current crash doesn't involve reading any old .o files. - Dan
Re: today's git does not compile
On Tue, Jan 18, 2011 at 12:55 PM, Dan Kegel wrote: > ... > It's not wine's fault, and you're not missing any dependencies; the > new version of gcc is probably buggy, and the bug is triggered by > something inside wine. If you've compiled Wine before and are re-using object files from an old gcc it's possible that there is a conflict between the object files from before and the object files with your new version of gcc. So, you could try a "make clean" and then compile again. Erich Hoover ehoo...@mines.edu
re: today's git does not compile
Susan wrote: > I have the latest version of Natty Narwhal > gcc (Ubuntu/Linaro 4.5.2-1ubuntu6) 4.5.2 >... >gcc -m32 -c -I. -I. -I../../include -I../../include -D__WINESRC__ >-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing >-Wdeclaration-after-statement -Wstrict-prototypes -Wtype-limits >-Wwrite-strings -Wpointer-arith -Wlogical-op -g -O2 -U_FORTIFY_SOURCE >-D_FORTIFY_SOURCE=0 -o pen.o pen.c >pen.c: In function ‘X11DRV_SelectPen’: >pen.c:31:12: internal compiler error: Segmentation fault >Please submit a full bug report, >with preprocessed source if appropriate. >See for instructions. It's not wine's fault, and you're not missing any dependencies; the new version of gcc is probably buggy, and the bug is triggered by something inside wine. Try switching from -O2 to -O1 with configure CFLAGS="-g -O1" and rebuild. Does that help? Regardless of whether that gets you past the problem, please file a bug in launchpad against gcc-4.5. https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/693686 and https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/690194 are similar bugs you could use as examples. Ideally they'd want you to run with -save-temps and give them a copy of pen.i.
Re: today's git does not compile
On 1/18/11 12:10 PM, Susan Cragin wrote: > pen.c:31:12: internal compiler error: Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. Looks like you've hit a compiler bug. Do what the error message says, and report this to the GCC guys. Chip
Re: Today's git does not compile
On Tue, Jan 20, 2009 at 9:10 AM, Susan Cragin wrote: > At least, it doesn't for me... > > O2 -o wowthunk.o wowthunk.c > ../../tools/winebuild/winebuild -D_REENTRANT -fPIC --as-cmd "as" -o > relay16asm.o --relay16 > ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_deu.mc.rc > nls/winerr_deu.mc > ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_enu.mc.rc > nls/winerr_enu.mc > ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_fra.mc.rc > nls/winerr_fra.mc > ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_kor.mc.rc > nls/winerr_kor.mc > ../../tools/wmc/wmc -i -U -H /dev/null -o nls/winerr_nor.mc.rc > nls/winerr_nor.mc > ../../tools/wrc/wrc --nostdinc -I. -I. -I../../include -I../../include > -D__WINESRC__ -D_KERNEL32_ -fokernel.res kernel.rc > Source: �̤� a2 cc a4 eb > Unicode: 5341 6708 > Back: �Q�� a4 51 a4 eb > nls/cht.nls:84:16: Error: String �̤� does not convert identically to Unicode > and back in codepage 950. Try using a Unicode string instead > make[2]: *** [kernel.res] Error 1 > make[2]: Leaving directory `/home/susan/wine/dlls/kernel32' > make[1]: *** [kernel32] Error 2 > make[1]: Leaving directory `/home/susan/wine/dlls' > make: *** [dlls] Error 2 > su...@ubuntu:~/wine$ > > > > > > Looks like Alexandre already committed a fix: http://source.winehq.org/git/wine.git/?a=commitdiff;h=6d0a0fb1820d80cd2b3fd643973329561848e8c1 -- -Austin
Re: today's git does not compile with yesterday's new gcc -- regression test results
>>> I did the regression test. But how legitimate are the results if the >>> problem is the new gcc that I downloaded recently, and not wine? This problem was an Ubuntu linux bug, and has been fixed in headers for kernel 2.6.28-2.2. See Ubuntu bug 303711. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/303711
Re: today's git does not compile with yesterday's new gcc -- regressiontest results
"Susan Cragin" [EMAIL PROTECTED] wrote: >I did the regression test. But how legitimate are the results if the problem >is the new gcc that I downloaded recently, >and not wine? > gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease) > > [EMAIL PROTECTED]:~/wine$ git bisect bad > Bisecting: 0 revisions left to test after this > [0b7478a79fb0594daba5cee3c024c352ad39] widl: Make sure format strings for > structure and union types are only > output once. >From http://wiki.winehq.org/RegressionTesting If you see: Bisecting: 0 revisions left to test after this THEN YOU ARE NOT DONE YET! -- Dmitry.
Re: today's git does not compile with yesterday's new gcc -- regression test results
On Sun, Nov 30, 2008 at 10:24:56AM -0500, Susan Cragin wrote: > I did the regression test. But how legitimate are the results if the problem > is the new gcc that I downloaded recently, and not wine? > gcc (Ubuntu 4.3.2-2ubuntu5) 4.3.3 20081129 (prerelease) > > [EMAIL PROTECTED]:~/wine$ git bisect bad > Bisecting: 0 revisions left to test after this > [0b7478a79fb0594daba5cee3c024c352ad39] widl: Make sure format strings for > structure and union types are only output once. Perhaps you can help showing by us the errormessage :) Ciao, Marcus
