I can't update my system via emerge --update --deep --newuse world Reproducible: Always Steps to Reproduce: 1. emerge --update --deep --newuse world 2. on xorg update error messege 3. update stopted Actual Results: update stopted Expected Results: Install the update of xorg The bug is not reproducible, so it is likely a hardware or OS problem. make[6]: *** [intel_tris.o] Error 1 make[6]: Leaving directory `/var/tmp/portage/xorg-x11-6.8.0-r4/work/xc/lib/GL/mesa/drivers /dri/i915' make[5]: *** [all] Error 2 make[5]: Leaving directory `/var/tmp/portage/xorg-x11-6.8.0-r4/work/xc/lib/GL/mesa/drivers /dri' make[4]: *** [all] Error 2 make[4]: Leaving directory `/var/tmp/portage/xorg-x11-6.8.0-r4/work/xc/lib/GL' make[3]: *** [all] Error 2 make[3]: Leaving directory `/var/tmp/portage/xorg-x11-6.8.0-r4/work/xc/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/tmp/portage/xorg-x11-6.8.0-r4/work/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/var/tmp/portage/xorg-x11-6.8.0-r4/work/xc' make: *** [World] Error 2 !!! ERROR: x11-base/xorg-x11-6.8.0-r4 failed. !!! Function src_compile, Line 266, Exitcode 2 !!! make World failed
I have an IBM NetVista type 6341-MMS with an intel chip set. I use the i810 driver on my present xorg-x11. I had quit some problems that realate to my computer. This can right before the error messeges: O2 -march=i686 -fomit-frame-pointer -fno-strict-aliasing XpJob.c -o unshared/XpJob.o In file included from /usr/include/sys/types.h:31, from ../../exports/include/X11/Xlib.h:52, from ../../exports/include/X11/extensions/Printstr.h:66, from XpJob.c:43: /usr/include/bits/types.h:-3299: internal compiler error: Segmentation fault
Same thing happens on my gentoo box. I get the !!! ERROR: x11-base/xorg-x11-6.8.0-r4 failed. !!! Function src_compile, Line 266, Exitcode 2 !!! make World failed Need more info? let me know what you need.
Carsten, doesn't sound like an X bug. ICE's are generally hardware or occasionally a broken toolchain. Matthew, please file a new bug if you've looked at bug #20600 and decided that's not your problem. *** This bug has been marked as a duplicate of 20600 ***
Found problem, it is my MMU that is damaged. I run memory test and all memory that I put in acts the same way. Thanks