Building project instsetoo
not found and couldn't be built. Correct build.lsts.
!!! ERROR: app-office/openoffice-1.1.0 failed.
!!! Function src_compile, Line 457, Exitcode 1
!!! Cannot find build directory!
Created attachment 20113 [details]
Full Compile Log
The error message produced in the compile is conflicting so I submitted the
Created attachment 20114 [details]
I'm running very conservative compile options for the Athlon 800. I'm running
full 'emerge sync && emerge -DU world' everynight and everything but openoffice
is up to date.
Could you attach
Created attachment 20133 [details]
OpenOffice Config Log
As requested, thanks for looking into this.
It seems that ccache is not correctly setup on daphnie. If it doesn't work,
try compiling without distcc or ccache
I'd already tried getting rid of ccache and distcc on 4 different systems
over the last month since this last release. I've been watching the daily
bug reports of openoffice. Finally decided to file my own. The error is always
the same no matter which CPU or setting or whether distcc and ccache were
The topography is as follows 300 Mhz Cyrix, 700&800 AMD and 900 AMD; mcpu=486
-O2, 586 -O2 and 686 -O3 respectively. Not using branded optimizations at
Over the past 6 months at least 2 of them have been able to successfully
compile openoffice when the new versions came out.
The only thing that sets these systems apart is that the USE= was changed
from gtk to gtk2 and all of Gnome was recompiled.
I just finished rebuilding a server with an XP2600 tonight and have started
the openoffice compile sans ccache and distcc, I'll report back the results.
The easiest way is just to run:
FEATURES="-distcc" emerge openoffice. This should cause distcc not to be
used. ccache on the local host is safe, but if you want to disable that too
FEATURES="-distcc --cache" emerge openoffice
Last night 3 systems had the same error as originally reported after running
"emerge -C distcc ccache" and then /etc/init.d/distccd stop.
The 4th system had the sandbox violation, I've seen reported elsewhere. It
was done compiling and just looking to write the files.
David, is this still a problem with more recent versions?
No feedback for quite some time, closing