during the merging of the masked package "app-office/openoffice-2.0.0" the compiler gives an error of Segmentation fault Reproducible: Always Steps to Reproduce: 1. edit package.unmask and add the name of Openoffice2's ebuild and his dependences 2. edit package.keywords 3. emerge '>=app-office/openoffice-2.0.0' Actual Results: Making: ../../unxlngi4.pro/slo/frame.obj g++ -Wuninitialized -fmessage-length=0 -c -I. -I. -I../inc -I../../inc -I../../unx/inc -I../../unxlngi4.pro/inc -I. -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/solver/680/unxlngi4.pro/inc/stl -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/solver/680/unxlngi4.pro/inc/external -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/solver/680/unxlngi4.pro/inc -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/solenv/unxlngi4/inc -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/solenv/inc -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/res -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/solver/680/unxlngi4.pro/inc/stl -I/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/solenv/inc/Xp31 -I/opt/blackdown-jdk-1.4.2.02/include -I/opt/blackdown-jdk-1.4.2.02/include/linux -I/opt/blackdown-jdk-1.4.2.02/include/native_threads/include -I/usr/include -I. -I../../res -I. -O1 -pipe -O2 -march=pentium4 -Wno-ctor-dtor-privacy -include preinclude.h -fexceptions -fno-enforce-eh-specs -fpic -DLINUX -DUNX -DVCL -DGCC -DC300 -DINTEL -DGXX_INCLUDE_PATH=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/include/g++-v3 -DCVER=C300 -D_USE_NAMESPACE -DGLIBC=2 -DX86 -D_PTHREADS -D_REENTRANT -DNEW_SOLAR -D_USE_NAMESPACE=1 -DSTLPORT_VERSION=400 -D__DMAKE -DUNIX -DCPPU_ENV=gcc3 -DSUPD=680 -DPRODUCT -DNDEBUG -DPRODUCT_FULL -DOSL_DEBUG_LEVEL=0 -DOPTIMIZE -DEXCEPTIONS_ON -DCUI -DSOLAR_JAVA -DOOO680 -DSHAREDLIB -D_DLL_ -DMULTITHREAD -o ../../unxlngi4.pro/slo/frame.o /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/framework/source/services/frame.cxx /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/framework/source/services/frame.cxx: In member function `void framework::Frame::implts_startWindowListening()': /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/framework/source/services/frame.cxx:3016: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. sandbox: Caught signal 2 in pid 18334 '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0/build/ooo680-m3/framework/source/services make: *** [stamp/build] Error 1 /usr/portage/app-office/openoffice/openoffice-2.0.0.ebuild: src_compile aborted; exiting. Expected Results: successful merging of openoffice my /etc/make.conf: ############################### # These settings were set by the catalyst build script that automatically built this stage # Please consult /etc/make.conf.example for a more detailed example CFLAGS="-O2 -march=pentium4" CHOST="i686-pc-linux-gnu" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j2" USE="gtk gnome -qt -kde dvd alsa arts cdr nvidia java browserplugin" GENTOO_MIRRORS="http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/" LINGUAS="it en" ###########################################
A few things: 1) Please provide the output of "emerge info", this is vital for tracking down bugs 2) Are you sure your harddisc didn't fill up during the build and you have enough RAM (256 MB+) 3) Can you reproduce the bug (does it fail at the EXACT same point when you try again?
Seems a candidate for being a duplicate of #20600 to me.
Yes, I would agree, especially the "flaky hardware"-part, maybe overheating cpu or something like that
here the output of 'emerge info': tslab nico # emerge info Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.13-gentoo-r3 i686) ================================================================= System uname: 2.6.13-gentoo-r3 i686 Intel(R) Pentium(R) 4 CPU 2.20GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/"LINGUAS="it en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts avi berkdb bitmap-fonts browserplugin cdr crypt cups curl dvd eds emboss encode esd fam foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imagemagick imlib ipv6 java jpeg junit libg++ libwww mad mikmod motif mozilla mp3 mpeg ncurses nls nvidia ogg oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl spell ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts udev vorbis xml xml2 xmms xv zlib linguas_it linguas_en userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY ------------------------------ my pc has 1024 MB of RAM. >does it fail at the EXACT same point when you try >again? yes, sure
Did you take a look at the bug Paul referenced? A segfaulting gcc should not be caused by OOo, so this most likely is a bug with your system or hardware
*** Bug 110601 has been marked as a duplicate of this bug. ***
No feedback for nearly a month, most likely a hardware problem, so closing
