BOTTOM LINE (even though it's at the top) It appears openoffice-bin depends on some things that are not marked in the ebuild.
My attempt to compile openoffice (not bin) failed due to disk space, but not until about 8 dependencies had been compiled. Openoffice-bin had not pulled them in. I never did complete the compile. I trimmed distfiles and packages and in other ways got up to 12 GB free space and emerged openoffice-bin. It runs fine now. This is not proof for various reasons, but I suspect the additional dependencies did the trick. Or maybe it was disk space. Not much else changed. ++ kevin On Thu, Sep 25, 2008 at 3:04 PM, Kevin O'Gorman <[EMAIL PROTECTED]> wrote: > On Thu, Sep 25, 2008 at 2:08 AM, Dirk Heinrichs > <[EMAIL PROTECTED]> wrote: >> Am Donnerstag 25 September 2008 05:37:14 schrieb ext Kevin O'Gorman: >> >>> > openoffice-bin has been compiled with a given set of use flags and on a >>> > machine that may or may not match what you have. Compiling it yourself is >>> > always the better idea. >>> >>> Not so obviously better when it fails. Here's the tail of what I get: >> >> You do have enough free space in the build directory (~6G)? >> >> Bye... >> > > Apparently not. I just had something else fail, and I'm moving stuff around. > That's probably a major part of what's plagueing me now. > > ++ kevin > > > -- > Kevin O'Gorman, PhD > -- Kevin O'Gorman, PhD
