so i emerge openoffice-1.1.0-r1, and after around 12 hours of compiling, we finally get to the stage where it installs into the image directory. then we fail out with: Replacing ${EVAL} with Replacing ${LONG_PRODUCTEXTENSION} with Replacing ${PRODUCTEXTENSION} with Replacing ${PRODUCTNAME} with OpenOffice.org Replacing ${PRODUCTVERSION} with 1.1.0 time needed: 0:0:55 WARNING! Project(s): gtk not found and couldn't be built. Correct build.lsts. flag-o-matic eutils gcc virtualx >>> Install openoffice-1.1.0-r1 into /rumba/tmp/portage/openoffice-1.1.0-r1/image/ category app-office * Installing OpenOffice.org into build root... glibc version: 2.3.2 Initializing installation program................... !!! ERROR: app-office/openoffice-1.1.0-r1 failed. !!! Function src_install, Line 536, Exitcode 1 !!! (no error message) i pasted in some context as well - perhaps the 'gtk project not found' message has something to do with it. i tried manually running 'setup -net' in /rumba/tmp/portage/openoffice-1.1.0-r1/work/oo_1.1_src/instsetoo/unxlngi4.pro/01/normal but no luck - it just pops up a little window with a progress bar - the bar fills up and then the app exits with no error message or anything (the app's exit code is 1, however). i'm going to be away for the next few days, so i won't be able to try anything out until monday or tuesday of next week. my emerge --info gives: Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r8, 2.6.0-test8-bk4) ================================================================= System uname: 2.6.0-test8-bk4 i686 AMD Athlon(tm) processor Gentoo Base System version 1.4.3.11 ccache version 2.2 [enabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-tbird -O3 -pipe -fforce-addr -falign-functions=4 -ffast-math" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /opt/tomcat/conf /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-tbird -O3 -pipe -fforce-addr -falign-functions=4 -ffast-math" DISTDIR="/usr/portage/distfiles" FEATURES="ccache autoaddcvs sandbox digest" GENTOO_MIRRORS="http://www.ibiblio.org/gentoo ftp://gentoo.noved.org/ http://adelie.polymtl.ca/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb alsa gdbm berkdb slang readline tetex aalib bonobo svga tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt motif opengl gphoto2 cdr 3dnow acpi4linux apache2 curl dvd fam fbcon ffmpeg flash gtk2 innodb joystick kerberos krb4 mmx nptl nvidia sasl stencil-buffer ungif usb v4l2 xfs xml xvid -kde -arts -mozilla"
I got the same failure here if I built openoffice with USE="gtk2" set. If I didn't set this env var, I got the following failure: Making: ../../unxlngi4.pro/slb/cmdparse.lib echo unxlngi4.pro/slo/cmdparse.o | xargs -n1 > ../../unxlngi4.pro/slb/cmdparse.lib ------------- /var/tmp/portage/openoffice-1.1.0-r1/work/oo_1.1_src/svtools/util using: ../unxlngi4.pro/slb/config.lib ../unxlngi4.pro/slb/filerec.lib ../unxlngi4.pro/slb/items1.lib ../unxlngi4.pro/slb/misc1.lib ../unxlngi4.pro/slb/notify.lib ../unxlngi4.pro/slb/passwordcontainer.lib ../unxlngi4.pro/slb/svarray.lib ../unxlngi4.pro/slb/svhtml1.lib ../unxlngi4.pro/slb/svrtf.lib ../unxlngi4.pro/slb/svsql.lib ../unxlngi4.pro/slb/cmdparse.lib using: ../unxlngi4.pro/slb/svl.lib ------------------------------ Making: ../unxlngi4.pro/slb/svl.lib dmake: Error -- `../unxlngi4.pro/slb/sbx.lib' not found, and can't be made ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.1.0-r1/work/oo_1.1_src/svtools/util !!! ERROR: app-office/openoffice-1.1.0-r1 failed. !!! Function src_compile, Line 465, Exitcode 1 !!! Build failed!
The gtk project message is irrelevant. It is only used for the crashreporter, and that is not build as it is pointless with a home-compiled openoffice. It seems that you have used overagressive compilation flags: Please try CXXFLAGS="-march=athlon-tbird -O2 -pipe" The ebuild does not depend on the gtk2 useflag at all.
I have: CFLAGS="-O3 -mcpu=pentium4 -march=pentium4 -fprefetch-loop-arrays -pipe" This has worked without problems on my system here to successfully build openoffice 1.0 and openoffice 1.1.0 (once I solved the xargs problem). This problem occurred only with openoffice-1.1.0-r1.
There are some patches in -r1 that enable compilation on development kernels and nptl systems. If you don't have that there is no reason to upgrade to -r1. Linday I cannot really see what is the cause of the sbx.lib failure. Maybe the full compilation log could help. However openoffice compilation can also fail because of external factors such as memory depletion. Often trying again works ok. Brian, I see that you use nptl and a development kernel. It could be that something goes wrong because of that. You could try compiling under a 2.4 kernel (if possible)
I ramped back my CFLAGS, which are now: CFLAGS="-O2 -mcpu=pentium -march=pentium -pipe" I set gtk2, which may not matter at all, and tried again. This morning I had the following failure: ------------------------------ Making: ../../unxlngi4.pro/slb/svsql.lib echo unxlngi4.pro/slo/converter.o | xargs -n1 > ../../unxlngi4.pro/slb/svsql.lib ------------- /var/tmp/portage/openoffice-1.1.0-r1/work/oo_1.1_src/svtools/util using: ../unxlngi4.pro/slb/config.lib ../unxlngi4.pro/slb/filerec.lib ../unxlngi4.pro/slb/items1.lib ../unxlngi4.pro/slb/misc1.lib ../unxlngi4.pro/slb/notify.lib ../unxlngi4.pro/slb/passwordcontainer.lib ../unxlngi4.pro/slb/svarray.lib ../unxlngi4.pro/slb/svhtml1.lib ../unxlngi4.pro/slb/svrtf.lib ../unxlngi4.pro/slb/svsql.lib ../unxlngi4.pro/slb/cmdparse.lib using: ../unxlngi4.pro/slb/svl.lib ------------------------------ Making: ../unxlngi4.pro/slb/svl.lib dmake: Error -- `../unxlngi4.pro/slb/eaimp.lib' not found, and can't be made ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.1.0-r1/work/oo_1.1_src/svtools/util !!! ERROR: app-office/openoffice-1.1.0-r1 failed. !!! Function src_compile, Line 465, Exitcode 1 !!! Build failed! I've had the build fail at this point before for r1. The system has 1G of physical memory with c.a. 1G of swap, so although it's possible that memory was exhausted, a build which consumed that much memory probably has inherent problems. If you'd like me to capture the build output I'll be glad to do so and post it as an attachment. In the meantime, I'll try a direct ebuild on the non-r1 version which I previously compiled successfully.
BTW, I built openoffice-1.1.0 (sans r1) with no problems.
> Brian, I see that you use nptl and a development kernel. It could be that > something goes wrong because of that. You could try compiling under a 2.4 > kernel (if possible) i've since removed nptl and recompiled glibc, as it was causing serious system instabilities, so i'm going to give openoffice (-r1) a try again, still with my 2.6 kernel. if that doesn't work i'll see about 2.4. if all else fails i'll give "-r0" a shot.
ok, i tried openoffice-1.1.0-r1 WITHOUT an nptl-enabled glibc and with USE='-nptl', and WITH a 2.6 kernel, and it compiled and installed correctly. i also used less agressive CFLAGS/CXXFLAGS as suggested (-march=athlon-tbird -O2 -pipe). i just started a compile with my original CFLAGS (-march=athlon-tbird -O3 -pipe -fforce-addr -falign-functions=4 -ffast-math) to see if something in there was the culprit, but i'm leaning toward thinking it's a pretty safe bet that the issues are coming from nptl.
yep, compile with my more-aggressive CFLAGS from the above comment was successful. nptl seems to be the culprit...
Image installation has nothing to do with CFLAGS or nptl-support, this is just another of the problems we had with virtualmake under some circumstances. Anyway, this should be fixed now in Portage (in 1.1.0-r2), so closing this bug
Andreas, aggressive CFLAGS or nptl can cause the installer to crash/segfault. That is what I was pointing at. Anyway, I'll leave it closed as there is not much we can do except removing the need for virtualmake.
