Description of problem: openoffice.org-core-1.9.104-1 is incompatible with the latest gcc-4.0.0-8 stack in dist-fc4, causing a dependency clash and upgrade failure. This is a FC4Blocker. What changed and why?
Umm, gcc-4.0.0-8 changed the AWT library from libjawt.so -> libgcjawt.so because proprietary VMs use libjawt and gcj shouldn't clash with them. While libgcjawt.so supposedly gets symlinked to libjawt.so, OOo currently relies upon "-ljawt". So, OOo uses a JAVA_HOME variable to point to the base of the JDK. Well, for GCJ that's "/usr" because that's where bin/java and bin/javac are rooted from. However, that's _not_ where the rest of the java libraries are... We should probably be pointing at "/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0" now, but that may clash with assumptions scattered around the code that were made before the java-gcj-compat packages were developed. I'm trying a build pointed to the new location, we'll see how it goes.
This should be marked as duplicate of bug #158411. And yes, I'm seeing it too :-(
*** Bug 158411 has been marked as a duplicate of this bug. ***
A fix for the gcjawt library is in CVS, and a new copy of OOo is building now to fix some utter berkeleydb stupidity (which was blocking the rebuild this weekend).
Package is building now.
*** Bug 158613 has been marked as a duplicate of this bug. ***
In response to Comment #1: On the compile line that specifies -ljawt, add (or modify the existing -L to be): -L%{_jvmdir}/java/jre/lib/%{_arch}
Actually, this should be: -L%{_jvmdir}/jre/lib/%{_arch}, since only java-1.4.2-gcj-compat may be installed (and not java-1.4.2-gcj-compat-devel). But looking at the spec file, you've linked directly to libgcjawt.so, which is fine too.
http://people.redhat.com/wtogami/temp/openoffice/ I copied binaries here for i386 for testing.