On Sat, Feb 01, 2003 at 05:55:41PM +0100, Stijn Vander Maelen wrote:
> > -I/usr/X11R6/include -I/usr/kde/3.1/include -I/usr/include/libart-2.0
> > -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long
> > -Wundef -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes
> > -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
> > -Wconversion -DNDEBUG -DNO_DEBUG -O2 -march=athlon-xp -O3 -pipe
> > -fno-exceptions -fno-check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE
> > -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -c -o kiconeffect.lo `test -f
> > 'kiconeffect.cpp' || echo './'`kiconeffect.cpp
> > In file included from /usr/qt/3/include/qobject.h:45,
> > from /usr/qt/3/include/qwidget.h:43,
> > from kiconeffect.cpp:24:
> > /usr/qt/3/include/qevent.h:450: internal error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://bugs.gentoo.org/> for instructions.
> > make[3]: *** [kiconeffect.lo] Error 1
> >
> > Seems like I'm going backwards rather than forwards here... any help
> > would be appreciated.
>
> signal 11's in the compiler are mostly caused by:
> - bad ram (run memtest)
> - your cpu is overheating
>
> regards,
> stijn
> >
> > Thanks,
That seems unlikely to me, unless this is the first thing he's
tried to compile (which is not likely on the gentoo list). If
you get a seg fault while compiling qt or libkde because of bad
memory or a cpu overheat, I think you would get it when compiling
anything of any size.
Probably unrelated, but I had trouble compiling qt stuff not long
ago when I would set the environment variable
__GL_SINGLE_THREADED=1. uic (and a couple of other programs)
would seg fault whenever I would try to run them. Setting this
environment variable to 1 was recommended not long ago for those
using the NVidia closed-source drivers. But I haven't had
trouble yet since I removed it.
- richard
--
Richard Kilgore
[EMAIL PROTECTED]
--
[EMAIL PROTECTED] mailing list
