Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 5636 - OpenOffice 1.0.0-r2 ebuild compile fails
Summary: OpenOffice 1.0.0-r2 ebuild compile fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: Normal normal (vote)
Assignee: Seth Chandler
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-26 23:55 UTC by Sean Bruton
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Bruton 2002-07-26 23:55:59 UTC
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...
Comment 1 Sean Bruton 2002-07-26 23:56:42 UTC
the "*" is red
Comment 2 Martin Schlemmer (RETIRED) gentoo-dev 2002-08-06 15:32:06 UTC
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 ?
Comment 3 James Cooper 2002-08-28 02:52:43 UTC
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.
Comment 4 Sven Vermeulen (RETIRED) gentoo-dev 2002-08-30 04:19:11 UTC
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.
Comment 5 CondorDes 2002-09-01 02:41:54 UTC
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...
Comment 6 Sven Vermeulen (RETIRED) gentoo-dev 2002-09-01 06:10:42 UTC
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). 
Comment 7 Seth Chandler 2002-11-29 11:48:10 UTC
this is fixed in the 1.0.1 ebuilds