| Summary: | OpenOffice 1.0.0-r2 ebuild compile fails | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sean Bruton <foo> |
| Component: | Current packages | Assignee: | Seth Chandler <sethbc> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 1.3 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
the "*" is red What version of portage are you using. Can you try to remove the openoffice dir from portage, and all downloaded files it needs, and rsync the tree again as well as downloading everything again ? Same problem here. (Occurs during install while hosted on another distro. Haven't booted into Gentoo to try this yet.) I tried nuking all OpenOffice related portage stuff, and keep getting the same thing. It looks like it might be dying in the middle of some message (see other OpenOffice bugs for some error messages.) Also, I'm trying to compile on a partition with not-gigantic (read over 4gig) space left. If it didn't take so blasted long, I'd try openoffice-bin, whatever that is. Will report on that later. On slightly old EPOX VIA Athlon setup, chrooted under RH7.something. Portage version is 2.0.28 according to emerge --version. I'm having the same troubles, using Gentoo 1.4beta (gcc-3.2-r1). I've tried making a symlink to /usr/bin/gcc called /usr/bin/gcc3, but no luck. I'm using portage 2.0.33 and am encountering the same problem, even after an 'emerge rsync'. I'm using Gentoo 1.2, and am relatively new to this distro, so I don't really have much of an idea what else I can do... I've advanced in this point. I've run a "strace emerge openoffice" and saw that a new process was forked. I kill -9'ed it and the emerge stopped, but It gave information about the blackdown-jdk. You had to execute some commands: ~# emerge blackdown-jdk (if you haven't done so already) ~# java-config --set-system-vm=blackdown-jdk-1.3.1 ~# env-update ~# source /etc/profile With this done, the emerge continue's (i.e. bug resolved :) but another bug surfaces (not related to this one anymore - gcc 3.2 related). this is fixed in the 1.0.1 ebuilds |
fark openoffice # ebuild openoffice-1.0.0-r2.ebuild compile >>> md5 ;-) OOo_1.0.0_source.tar.bz2 >>> md5 ;-) gpc231.tar.Z >>> md5 ;-) openoffice-1.0.0b-registry.tbz2 * I put an "echo starting compile" at the top of the src_compile() function in the ebuild script and it never gets executed...