Bug 60183

Summary: Intermittent gcc internal errors compiling kde
Product: [Retired] Red Hat Linux Reporter: Bryce Nesbitt <bryce>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-02-21 15:23:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bryce Nesbitt 2002-02-21 15:23:32 UTC 
I get periodic gcc internal errors compiling kde.  I have to restart the compile
several
times for it to finish:

c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/home/bryce/kdetest/include
-I/home/bryce/cvs/kde/qt-copy/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT
-D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wbad-function-cast -Wundef -Wall
-pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -fno-builtin -g -O2
-fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT
-DQT_NO_ASCII_CAST -Wp,-MD,.deps/kwinbutton.pp -c kwinbutton.cpp  -fPIC -DPIC -o
.libs/kwinbutton.o
kwinbutton.cpp: In method `KWinInternal::KWinToolTip::~KWinToolTip ()':
kwinbutton.cpp:80: Internal error: Segmentation fault.
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
gmake[3]: *** [kwinbutton.lo] Error 1
gmake[3]: Leaving directory `/mnt/bigstuff/cvs/kde/kdebase/kwin'

HardHat:kdebase> gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)

It's not repeatable on any one file.  Usually if I cd to the directory in
question and
gmake there, I can get past the blockage.  I know it does not make any sense.
Comment 1 Jakub Jelinek 2002-02-22 13:55:11 UTC 
It makes sense. In 99% of cases something like this has been reported,
it has been because of flaky hardware.