When emerging Openoffice, the src_install() fails with little debug information. Here's what happened: copy file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/program/libmcnttype.so unpack file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/share/dtd/officedocument/1_0/script.mod unpack file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/share/config/webcast/poll.pl unpack file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/program/spadmin.bin unpack file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/program/libspell645li.so unpack file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/share/dtd/officedocument/1_0/drawing.mod copy file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/program/libregmimetypes645li.so unpack file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/program/libdict_ja.so unpack file: /var/tmp/portage/openoffice-1.1.0-r1/image//opt/OpenOffice.org1.1.0/share/psprint/driver/fontunxppds.zip !!! ERROR: app-office/openoffice-1.1.0-r1 failed. !!! Function src_install, Line 522, Exitcode 1 !!! (no error message) The 1.1.0-r1 ebuild I'm using is identical to 1.1.0 except for the addition of a patch to fix some compile problems I was having. That patch is attached to bug 30335. I have not yet tried to reproduce this bug, as compiling OO on my system (800 mhz Crusoe) takes a number of days. Reproducible: Didn't try Steps to Reproduce: Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.6.0-test6-mm4) ================================================================= System uname: 2.6.0-test6-mm4 i686 Transmeta(tm) Crusoe(tm) Processor TM5800 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -pipe -fomit-frame-pointer -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0" 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 /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=i686 -pipe -fomit-frame-pointer -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox autoaddcvs -ccache" GENTOO_MIRRORS="http://mirror.calvin.edu/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://mirror.calvin.edu/gentoo-portage" USE="oss foomaticdb gnome libg++ libwww mad mikmod nls gdbm berkdb slang bonobo guile sdl gpm tcpd python esd imlib acpi -afs alsa apm arts avi cdr crypt cups dvd encode gd gif gtk gtk2 imap ipv6 java jpeg kde kerberos ldap -lirc mmx motif mozilla mpeg mysql ncurses oggvorbis opengl pam pdflib perl png qt quicktime readline samba sasl spell ssl svga tiff truetype usb X xml2 xmms xv zlib x86"
If you have the full compile log, please attach it. What you could try to do is to go to the /var/tmp/portage/openoffice-1.1.0/work/openoffice-1.1.0/instsetoo/unx??pro/1/ directory (or very similar name) and run setup -net from there on some directory in /tmp (or something). That might give you extra information on what failed
Well, running setup -net completed the install successfully. Maybe it's a sandbox issue? Otherwise, feel free to close this bug if you don't think it's worth pursuing. Thanks for your help.
I had a similar issue with my install and was using the same ebuild because I'm building on 2.6.0-test7. I got some more error messages, though that may be helpful. The sandbox had some ACCESS ERRORS and the log file of those is: open_wr: /opt/OpenOffice.org1.0.3/foo.tmp unlink: /opt/OpenOffice.org1.0.3/delme Neither of those files exist, so that is where the error originates. I, too, was able to successfully finish installing using the setup -net command, but now ooffice and friends still point to 1.0.3 instead of 1.1.0
The openoffice setup program wants to upgrade. We don't want that as it violates the sandbox. I'll try to look into preventing it to doing this. What should also work is either using FEATURES="userpriv" or removing /root/.sversionrc
Using portage of 29-02-2004 I get pretty much the same error: unpack file: /var/tmp/portage/openoffice-1.1.0-r2/image//opt/OpenOffice.org1.1.0/share/config/webcast/poll.asp unpack file: /var/tmp/portage/openoffice-1.1.0-r2/image//opt/OpenOffice.org1.1.0/program/libxmlfa645li.so unpack file: /var/tmp/portage/openoffice-1.1.0-r2/image//opt/OpenOffice.org1.1.0/program/libxsltdlg645li.so copy file: /var/tmp/portage/openoffice-1.1.0-r2/image//opt/OpenOffice.org1.1.0/share/readme/README01 unpack file: /var/tmp/portage/openoffice-1.1.0-r2/image//opt/OpenOffice.org1.1.0/program/resource/fwe64501.res unpack file: /var/tmp/portage/openoffice-1.1.0-r2/image//opt/OpenOffice.org1.1.0/share/gallery/www-graf/gallwwwgraf.zip !!! ERROR: app-office/openoffice-1.1.0-r2 failed. !!! Function src_install, Line 541, Exitcode 1 !!! (no error message) My important data: Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.25) ================================================================= System uname: 2.4.25 i686 Intel(R) Pentium(R) III Mobile CPU 1200MHz Gentoo Base System version 1.4.3.10 Autoconf: sys-devel/autoconf-2.58 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" USE="X acpi alsa apm arts avi berkdb cdr crypt cups encode foomaticdb gdbm gif gphoto2 gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl pam pdflib perl png ppds python qt quicktime readline sdl slang spell ssl svga tcltk tcpd tetex truetype usb x86 xml2 xmms xv zlib" CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe" Using "setup -net" installs the files correctly...
Could you please attach a longer log (ebuild /usr/portage/app-office/openoffice-1.1.0-r2.ebuild install &>/tmp/oo-install.log) as it is not clear from this log what went wrong.
no response for 6 months.
