Recently, there have been some notible fixes to apache and openffice in the tree that I'm looking for some people to beat on to make sure they are fixed.

apache has in the past not been able to listen on mulitple ports by default. This is most noticible when people try to run mod_ssl. More information is documented in bug #7172 (http://bugs.gentoo.org/show_bug.cgi?id=7172). This appears to be fixed now. Looking for people particularly with high loads to beat up on this.

openoffice in the past hasn't been able to compile. Now thanks to some patches this is no longer the case. This will take you at least a day and a half on a 300MHz system, so set aside some time.

As an exercise, I tried the build on a U60-SMP (2x450); it took 20 hours
to build and install.

It might have taken less if it used MAKEOPTS for parallelism determination
instead of its own ECPUS environment variable. (Although ebuild file
seems to imply that a parallel make will fail.)

Build and install seem to go fine.

I will be able to do little or no testing, however, because:

I really don't have any use for it;

I have no documentation for it;

Most anything I try causes it to lock up, anyway (Here, "try" means
moving the cursor around over the openoffice window, press the 'help' button, things like that. "Lock up" means "go to some other screen
and use 'kill -9 xxx'.")

This particular system is completely up-to-date and standard from
openoffice's point of view, I would think, except that I am using
the ~sparc version of binutils. (It is '-kde -gnome' in case that matters.)

So, it does build and install, but for me, at any rate, I'd say it's not ready
for prime time. I wouldn't know how to begin to turn this into a useful bug
report beyond the subject line of this thread: Try openoffice on sparc and
see what happens.

> I compiled openoffice-1.1_rc3 from portage last night. It installed fine
> (no errors) and I can start oowriter and oodraw; however, if I try to open
> anything in the menus like file -> open then openoffice crashes hard. It
> starts drawing the frame of the "open" window, but about then it crashes.
> It's so bad that alt+sysrq+<anykey> doesn't work. I'm forced to push the
> reset button. I was wondering if anyone else has similar problems with
> oo_rc3? And possibly has a fix ?
> Thanks.
>
> Athlon-tbird
> Xfree-4.3.0-r2
> gcc-3.2.3-r1
>

Different version of openoffice (1.1-r3 vs 1.0.3-r1), different CPU, same
xfree, gcc, and hang.

As you were posting your reply, I had started up an 'emerge kde' and will rebuild with
'USE=kde', because it occured to me that my 'USE=-kde -gnome' is probably unusual. I'll
let you know after the cycle finishes (I left the kde install running overnight, and the
openoffice rebuild will finish long after that )

I don't know why openoffice would care about kde, but from the ebuild, it looks like it
does, and exactly in the area that locks up.

Concerning openoffice. I installed kde (3.1.2) and rebuilt openoffice
with USE=kde. It still locks up on any of the View, Tool,
etc. dropdown items. Otherwise, it seems to work.

Running from kde makes no difference.

I would guess that someone who knew openoffice internals could diagnose
this pretty quickly, but I am not that person.

The only non-standard thing about the U60 is that it has Keith Weslowski's
semctl patch installed in the kernel, and a quick reboot with the standard
2.4.21-r1 kernel shows that that makes no difference.

(By the way, on my system, ECPUS=2 is a bad idea, since it kills the build.)

If anyone has any good ideas, I can try again in a week or so, but for now
I'm taking it off the system (it uses much to much disk space.)

I FINALLY got OpenOffice compiled. Only took a few days. I'm experiencing the same issues as Ferris. Clicking 'File' causes total lockup, etc. I'm using a very simple build, not special features, etc. Stock kernel, lots of USE flags, but nothing too crazy (I think), and I'm NOT using '~sparc' by default.

For the builds, sfaulconer's build and mine should be considered identical, as
should the hardware and pretty much everything else.

I used ACCEPT_KEYWORDS='~sparc' only for the openoffice emerge.
Otherwise, I don't use it either. I used it here only so that the build
would take whatever ebuild file it wanted, rather that the one I forced it
to take. As I think I mentioned, the only think openoffice needed that I
didn't already have was jdk, ant it isn't masked.