Here is what I have found thus far.  I have done some functional
testing but I would be grateful for your assistance in verifying
and correcting.  This is all referencing the 2.0.2 sources as
available for download at
http://download.openoffice.org/2.0.2/source.html
(which is not all that easy to find from the home page).

The Linux-PAM headers are documented as a required dependency
on Linux, though not in a terribly obvious place.
I do not address building without these headers, though you
may choose to.  I have no easy way to test this case at this point.
It might be simplest to tar up the headers so they can be slapped
into the include directory rather than patch things in the build,
or give some instructions for doing this from the PAM tarball.
http://tools.openoffice.org/dev_docs/build_linux.html

There was a problem in 2.0.0 locating the NSPR headers when NSS
was installed system wide.  This has been corrected in 2.0.2.

If using the system installed Java, ensure that JAVA_HOME is
set to its location, e.g.

/opt/jdk1.5.0_06

Also ensure that the library directories, e.g.

/opt/jdk1.5.0_06/jre/lib/i386
/opt/jdk1.5.0_06/jre/lib/i386/xawt

are in /etc/ld.so.conf and run ldconfig if needed.  The xawt
directory is needed to locate libmawt.so.  The build uses the
presence of a definition of JAVA_HOME to determine that the system
installed Java is to be used rather than the one included in the
OpenOffice distribution.  I have not found a --with and --without
control on this.

The --with-system-db option has caused confusion.  It refers not
to the Java bindings of the Berkeley DB installed in LFS but to
a different product written in Java named Berkeley DB Java Edition.
http://www.sleepycat.com/products/bdbje.html
In all probability this is not installed and the --with-system-db
option should not be given.

I made patches to fix the following build problems.  None of the other
patches in the 2.0.0 build instructions have been applied.

Still a few sources fail to compile under Java 1.5 due to use of enum
as an identifier.  In Java 1.5, enum is a new reserved word.

The --with-firefox configuration selection is not honored in the extensions
build.  The build accesses the potentially nonexistent mozilla-plugin.pc
rather than firefox-plugin.pc.  It was necessary to change the configuration
system to export the --with-firefox setting in variable SYSTEM_FIREFOX
(which is valid only if SYSTEM_MOZILLA is equal to YES) in order to have
this accessible to the place in the build where it must be tested.

The filter configuration build fails when the system Java is used.  There are
three problems within the makefile:

	The guard tests for JDK equal to gcj, rather than for any host Java
	system being used.  The correct test is JAVA_HOME not null.

	An incorrect (undefined) variable is used to locate the xalan classes.
	The correct variable is STAR_RESOURCEPATH.

	The makefile fails to distinguish between setting an environment variable
	and setting a makefile variable, so the code that sets the makefile
	variable is ineffective in assisting with class resolution.  Change
	the makefile to pass the -classpath argument instead.

	(In 2.0.0, this failure situation went undetected and caused the
	resulting build to throw an exception immediately upon startup.
	In 2.0.2 this situation was detected and caused a build failure.)

The packaging system fails when --disable-odk is selected.

	This patch is still to be developed at this writing, but the required
	behavior is understood.  Until then the --disable-odk option cannot be
	given.

	(In process of trying this I learned that their build utility dmake
	only supports a half dozen or so functions and findstring is not among
	them.  Caveat if you are ever having to change something.)

The slap-in-new-beanshell/configure/build/install instructions remain valid
with the following modifications.  The build is six hours on my system.
 
The build result directory is changed (yet deeper!)

cd instsetoo_native/unxlngi6.pro/OpenOffice/native/install/en-US/linux-2.6-intel/buildroot/opt
cp -a -v openoffice.org2.0 /opt/openoffice-2.0.2

I did not find the claim "If you have installed desktop-file-utils-0.10
and use KDE, there is no further configuration necessary." to be true.  I
needed to do the by-hand .desktop file copy on a KDE system in order to have
the applications appear in the menus.