Hey everybody,
I've been trying to compile wine since version 1.0 and have gotten crashes during the make command, about 20 minutes in. Very frustrating.
I'm running Fedora 9, and I believe gcc version 4.3.0.8. Is this a gcc problem? If so, what can I do to fix it?
Output of failed make command follows...
gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o input.o input.c
gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o listbox.o listbox.c
gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o menu.o menu.c
gcc: Internal error: Segmentation fault (program cc1)
Please submit a full bug report.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
make[2]: *** [menu.o] Error 1
make[2]: Leaving directory `/tmp/wine-1.1.4/dlls/user32/tests'
make[1]: *** [user32/tests] Error 2
make[1]: Leaving directory `/tmp/wine-1.1.4/dlls'
make: *** [dlls] Error 2
Segmentation fault during compilation
-
- Newbie
- Posts: 2
- Joined: Tue Sep 23, 2008 7:58 pm
Segmentation fault during compilation
On Tue, 2008-09-23 at 20:09 -0500, steadyneddy wrote:
CPU or memory. This is particularly the case if you're segfaulting in
different places each time. You can try memtest86 ( or whatever it's
called ) to check your memory ( but I think gcc is supposed to be much
more taxing on your memory than memtest86 ). You can also underclock
your CPU ( is it currently overclocked ? )
version of gcc-4.3.0 on many different Gentoo systems, and I *never* got
segfaults. Maybe you've found an obscure gcc bug, but I doubt it. It's
far more likely that you've got hardware issues.
Dan
Daniel Kasak / DNA
Application Developer
T: +61.2.8968.4056 / F:
+61.2.9904.5055
[email protected]
24/7 Real Media
15-19 Parraween Street
Cremorne, NSW 2090
Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-us ... chment.htm
The usual cause of segfaults during compiling is bad hardware - eitherHey everybody,
I've been trying to compile wine since version 1.0 and have gotten
crashes during the make command, about 20 minutes in. Very
frustrating.
CPU or memory. This is particularly the case if you're segfaulting in
different places each time. You can try memtest86 ( or whatever it's
called ) to check your memory ( but I think gcc is supposed to be much
more taxing on your memory than memtest86 ). You can also underclock
your CPU ( is it currently overclocked ? )
I don't know about this *exact* version of gcc, but I ran variousI'm running Fedora 9, and I believe gcc version 4.3.0.8. Is this a gcc problem? If so, what can I do to fix it?
version of gcc-4.3.0 on many different Gentoo systems, and I *never* got
segfaults. Maybe you've found an obscure gcc bug, but I doubt it. It's
far more likely that you've got hardware issues.
Dan
Daniel Kasak / DNA
Application Developer
T: +61.2.8968.4056 / F:
+61.2.9904.5055
[email protected]
24/7 Real Media
15-19 Parraween Street
Cremorne, NSW 2090
Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-us ... chment.htm
Re: Segmentation fault during compilation
This is a known Fedora's problem. Run 'ulimit -s unlimited' before compiling Wine.steadyneddy wrote:Hey everybody,
I've been trying to compile wine since version 1.0 and have gotten crashes during the make command, about 20 minutes in. Very frustrating.
I'm running Fedora 9, and I believe gcc version 4.3.0.8. Is this a gcc problem? If so, what can I do to fix it?
Segmentation fault during compilation
gcc --versionI don't know about this *exact* version of gcc, but I ran various
version of gcc-4.3.0 on many different Gentoo systems, and I *never* got
segfaults. Maybe you've found an obscure gcc bug, but I doubt it. It's
far more likely that you've got hardware issues.