I've got Gentoo Linux Kernel:2.6.11-gentoo-r6 My use Flags: USE="-gtk -gnome qt kde dvd alsa cdr" I tried to emerge openoffice and here is the output: /var/tmp/portage/openoffice-1.1.4-r1/work/configmgr/source/treemgr/viewstrategy.cxx:706: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. dmake: Error code 1, while making '../../unxlngi4.pro/slo/viewstrategy.obj' ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.1.4-r1/work/configmgr/source/treemgr !!! ERROR: app-office/openoffice-1.1.4-r1 failed. !!! Function src_compile, Line 424, Exitcode 1 !!! Build failed! !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Emerge succefully OpenOffice from the portage tree.
Most likely your hardware is broken or you ran out of ram (compiling OOo needs about 2 GB iirc).
To be exact: You need 4+ GB of diskspace and 256 MB of RAM.
Hi! I want to compiel OO on a notebook... Hardware data: root partition Free disk space: 26.8gb Swap space: 1gb CPU: 3.3ghz Mobile Intel Memory: 1gb
Created attachment 57078 [details] OO-screenshot A screenshot from the system monitor while emerging OO
Could you attach a build log. The screenshot does not contain all the information. However based on the screenshot it seems that there is something very weird about your compiler.
Also could you please post the output of "emerge info" without that, there is nothing we can do...
Created attachment 57082 [details] Emerge log Emerge log, after compiling error from OO
Created attachment 57083 [details] Emerge Info
You said, there is something wrong with my gcc... here is gcc -v, perhaps it helps: gcc -v > /root/Desktop/gcc-v Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/specs Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/hardened.specs Configured with: /var/tmp/portage/gcc-3.3.5.20050130-r1/work/gcc-3.3.5/configure --enable-version-specific-runtime-libs --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.3.5-20050130 --includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3.5-20050130/info --with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/include/g++-v3 --host=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --disable-multilib --disable-libgcj --enable-languages=c,c++,f77 --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 3.3.5-20050130 (Gentoo Linux 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)
We need the output of the emerge command, not emerge.log
Created attachment 57085 [details] Emerge output of xtrem
Ok, in some way you've hit a compiler bug. That's probably related to using a hardened compiler. The rest of your compilation flags are benign enough allthough compiling for a p4 mobile you might want to at least add "-mtune=pentium4". Code compiled with that will still run on i686.
Hi! Hmm. i did it, and now, thats the output: Calculating dependencies ...done! >>> emerge (1 of 1) app-office/openoffice-1.1.4-r1 to / >>> md5 files ;-) openoffice-1.1.4-r1.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) files/digest-openoffice-1.1.4-r1 >>> md5 files ;-) files/1.1.4/gcc34.patch.bz2 >>> md5 files ;-) files/1.1.4/pyunolink-fix.patch >>> md5 files ;-) files/1.1.4/ooffice-wrapper-1.3 >>> md5 files ;-) files/1.1.4/gcc-instlib.patch >>> md5 files ;-) files/1.1.4/openoffice-java.patch >>> md5 files ;-) files/1.1.4/javafix.patch >>> md5 files ;-) files/1.1.4/hardened-link.patch >>> md5 files ;-) files/1.1.4/getcompver.awk.patch >>> md5 files ;-) files/1.1.4/cws-heapbug_CAN-2005-0941.diff >>> md5 files ;-) files/1.1.4/gcc34-nojava-fix.patch >>> md5 files ;-) files/1.1.4/pthreadlink-fix.patch >>> md5 files ;-) files/1.1.4/freetype-217.patch >>> md5 files ;-) files/1.1.4/nptl.patch >>> md5 files ;-) files/1.1.4/gcc34-sal-link-to-libsupc++.diff >>> md5 files ;-) files/1.1.4/STLport-vector.patch >>> md5 files ;-) files/1.1.4/newstlportfix.patch >>> md5 src_uri ;-) OOo_1.1.4_source.tar.gz >>> md5 src_uri ;-) STLport-4.6.2.tar.gz * * It is important to note that OpenOffice.org is a very fragile * build when it comes to CFLAGS. A number of flags have already * been filtered out. If you experience difficulty merging this * package and use agressive CFLAGS, lower the CFLAGS and try to * merge again. * * Please note that this package now uses the LINGUAS environment * variable to provide localization. The old LANGUAGE=ENUS|PORT... * system does NOT work anymore. * * If you want localized helpcontent, please download the correct file * for your language from an OpenOffice.org-mirror * (directory /contrib/helpcontent/ e.g.) and put it in your * /usr/portage/distfiles, the ebuild will use it automatically. * * Installing OpenOffice.org for US English (default) environment. >>> Unpacking source... >>> Unpacking OOo_1.1.4_source.tar.gz to /var/tmp/portage/openoffice-1.1.4-r1/work >>> Unpacking STLport-4.6.2.tar.gz to /var/tmp/portage/openoffice-1.1.4-r1/work * Applying newstlportfix.patch ... [ ok ] * Applying gcc-instlib.patch ... [ ok ] * Applying javafix.patch ... [ ok ] * Applying getcompver.awk.patch ... [ ok ] * Applying cws-heapbug_CAN-2005-0941.diff ... [ ok ] * Applying freetype-217.patch ... [ ok ] * Applying openoffice-java.patch ... [ ok ] * Applying gcc34.patch.bz2 ... [ ok ] * Applying gcc34-sal-link-to-libsupc++.diff ... [ ok ]>>> Source unpacked. ******************************************************************** * * * OpenOffice.org build configuration. * * * * The configure proces checks your platform to see whether * * you can build OpenOffice.org on it. * * This proces checks all pre-requisites and generates a file * * containing the necessary environment variables. * * Source this file after configure has ended successfully. * * * * Any warning that is generated during the configure process * * must be taken into account, since it can be a reason for * * an unsuccessfull build of OpenOffice.org * * * ******************************************************************** ******************************************************************** * * * Checking the platform pre-requisites. * * * ******************************************************************** checking for gawk... gawk checking for gawk... /bin/gawk checking for sed... /bin/sed checking the operating system... checked (Linux) checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. !!! ERROR: app-office/openoffice-1.1.4-r1 failed. !!! Function src_compile, Line 345, Exitcode 77 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. I think i had to undo t, or not?
Bloody hell. Should be -mcpu, not -mtune with the 3.3 series. In 3.4 it's renamed to -mtune. In any case that compile flag should not get openoffice to compile. It should just run a bit faster.
oO sry, i use linux just since a few weeks -.- So, what can be the problem of the OO?
Probably the hardened compiler. You might also want to test a compiler from the 3.4 series.
@gEry: The build output you attached shows a totally different build failure than your original bug report. Failing at different places normally points to a hardware problem. Could it be that your cpu gets too during compiling?
Closing, hardware problem
Hi! Yes it still was an hardware problem... i re-installed gentoo with the livecd 2004.3 and 2005.0 and i had always the same problem.It was either not possible to install gcc-03.4.3, a hardware problem to... thx for your help!