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.
On 19 January 2011 12:41, Susan Cragin susancra...@earthlink.net 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
On Wed, Jan 19, 2011 at 4:46 AM, Reece Dunn mscl...@googlemail.com 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
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.
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
Could there be a new dependency that isn't summoned by build-dep?
Or is it me?
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
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 file:///usr/share/doc/gcc-4.5/README.Bugs for instructions.
Looks like you've hit a compiler bug. Do what the error
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
On Tue, Jan 18, 2011 at 12:55 PM, Dan Kegel d...@kegel.com 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
On Tue, Jan 18, 2011 at 12:04 PM, Erich Hoover ehoo...@mines.edu wrote:
On Tue, Jan 18, 2011 at 12:55 PM, Dan Kegel d...@kegel.com 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
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
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
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.
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
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
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
16 matches
Mail list logo
