Segmentation fault when building kdelibs

Pat Maddox pergesu at gmail.com
Mon Sep 19 15:04:13 PDT 2005


On 19 Sep 2005 16:17:03 -0400, Lowell Gilbert
<freebsd-questions-local at be-well.ilk.org> wrote:
> Pat Maddox <pergesu at gmail.com> writes:
> 
> > I'm trying to upgrade my system, and the build of kdelibs always fails
> > because of some segmentation fault.  I have absolutely no idea what
> > all this means, so I'll try to post as much of the error as I can
> > determine is relevant.  Hopefully somebody can help me out.
> >
> > In file included from kjanuswidget.cpp:24:
> > /usr/X11R6/include/qheader.h:207: internal compiler error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> > gmake[3]: *** [kjanuswidget.lo] Error 1
> > gmake[3]: Leaving directory `/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2/kdeui'
> > gmake[2]: *** [all-recursive] Error 1
> > gmake[2]: Leaving directory `/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2/kdeui'
> > gmake[1]: *** [all-recursive] Error 1
> > gmake[1]: Leaving directory `/usr/ports/x11/kdelibs3/work/kdelibs-3.4.2'
> > gmake: *** [all] Error 2
> > *** Error code 2
> >
> > Stop in /usr/ports/x11/kdelibs3.
> > ** Command failed [exit code 1]: /usr/bin/script -qa
> > /tmp/portupgrade31298.0 make
> > ** Fix the problem and try again.
> > ** Listing the failed packages (*:skipped / !:failed)
> >         ! x11/kdelibs3 (kdelibs-3.4.0_1)        (segmentation fault)
> > --->  Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
> 
> The obvious question is: does it always fail at the same point?  If
> not, then it's almost certainly a hardware problem.  If it does, then
> a bit more information on your system would be needed, including how
> you updated the ports skeletons, and whether you tried updating them
> again since you first saw the problem.  And if you aren't already, try
> using the system compiler to build the port.
> 

I've had a couple people suggest that it may be a hardware problem -
what should I be looking for?


More information about the freebsd-questions mailing list