When trying to emerge openoffice, the ebuild fails on src_compile. It may be noteworthy that the last "*" is red in color. The process has to be killed with a CTRL-C Calculating dependencies ...done! >>> emerge app-office/openoffice-1.0.0-r2 to / >>> md5 ;-) OOo_1.0.0_source.tar.bz2 >>> md5 ;-) gpc231.tar.Z >>> md5 ;-) openoffice-1.0.0b-registry.tbz2 * !!! Portage interrupted by SIGINT; exiting. PORTAGE: Checking for Sandbox (setup)... PORTAGE: No Sandbox running, deleting /etc/ld.so.preload! Killed
Forgot to mention that the emerge "hangs" at the red asterisk.
rm /tmp/sandboxpid*
Deleting the sandbox pid files have no effect. it's being discussed in this thread: http://forums.gentoo.org/viewtopic.php?t=9677 Someone states a GCC3 requirement is being called inside the ebuild that shouldn't be.
Correction on the above.. GCC *is* required, but on some machines the error message is not appearing and the emerge freezes...please check that thread :)
GCC3, that is. Sorry :-/
---------------------------------------cut------------------------------------ *portage-2.0.34 (01 Sep 2002) 01 Sep 2002; Daniel Robbins <drobbins@gentoo.org>: portage.py, ebuild.sh: Azarah's ebuildsh() removed, various other little fixes like pkg_preinst and friends not dying on non-zero return codes. 01 Sep 2002; Martin Schlemmer <azarah@gentoo.org> ebuild.sh: add a custom version of the esyslog() function to fix the "Red Star" bug if no logger is running. ------------------------------------------------------------------------------- Please update portage.