This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
GCC 3.2 Segfaults...
- From: Chris Shepherd <chriss at whstuart dot com>
- To: GCC Help Mailing List <gcc-help at gcc dot gnu dot org>
- Date: Fri, 18 Oct 2002 15:00:41 -0400
- Subject: GCC 3.2 Segfaults...
Hi,
I'm having a problem with GCC 3.2 segfaulting on me while I'm compiling
various applications. I had intended on upgrading to glibc 2.3, which requires
GCC 3.x (3.2 specifically, if I'm not mistaken), so I upgraded it. All the self-
tests passed, so I installed it after removing GCC 2.96 (the default on my
RedHat 7.1 install).
Now, as I am also in the midst of upgrading to KDE 3.0 from source, I needed to
compile QT as well. So I grabbed the QT 3.0.5 packages from Trolltech's site,
unpack it, configure it, everything goes fine until part way through the actual
compile process.
I get the following error (paths shortened for brevity):
In file included from qt/include/qobject.h:45,
from qt/include/qwidget.h:43,
from widgets/qheader.h:42,
from widgets/qheader.cpp:38:
qt/include/qevent.h:528: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [.obj/release-shared-mt/qheader.o] Error 1
I checked with several people, and they have compiled the exact same source
packages without incident on GCC 2.95. I even went as far as sending the
packages to them to make sure it wasn't package related, and they had no
problems.
Anyone have any ideas?
When I configured GCC 3.2, I did:
./configure
make bootstrap
make
make install
If I remember correctly.
I'm almost certain this is a user related issue, since I know other people MUST
have compiled the same packages using GCC 3.x, otherwise there would be
something in the package's FAQ about it. Can anyone tell me what I did wrong?
--
Chris Shepherd
-------------------------------------------------
This email may contain confidential information. Use of any such information
is strictly prohibited without express written consent of the sender