It is so a CFLAGS issue. Let me explain, the installation fail when after compiling OOo register its components
before installing. It register them with a program that has just been _compiled_ during the OOo compilation.
This program is fragile and will exhibit strange behavior and break when compiled with certain CFLAGS, programs
can break with some optimizations and this one could be one of those cases. Some time ago a problem was
happening when the _external_ (separate ebuild) spell checking program was compiled with the wrong CFLAGS, it
was happening at registration as well - so a program that is "over-optimized" can somehow break the registration
as well.

Now unless you did something to clean you /var/tmp/portage directory or restarted the compilation, the
log file should still be there. Open it, with emacs for example, and search for the string "ERROR" and report
all occurences please.

I had the same problem and I solved it by changing my CFLAGS to the ones I posted above.

Quote:

It is so a CFLAGS issue. Let me explain, the installation fail when after compiling OOo register its components
before installing. It register them with a program that has just been _compiled_ during the OOo compilation.
This program is fragile and will exhibit strange behavior and break when compiled with certain CFLAGS, programs
can break with some optimizations and this one could be one of those cases. Some time ago a problem was
happening when the _external_ (separate ebuild) spell checking program was compiled with the wrong CFLAGS, it
was happening at registration as well - so a program that is "over-optimized" can somehow break the registration
as well.

Now unless you did something to clean you /var/tmp/portage directory or restarted the compilation, the
log file should still be there. Open it, with emacs for example, and search for the string "ERROR" and report
all occurences please.

If you can tell me exactly which gcc flag is causing the trouble, then we can do something about it, but unfortunately since it's such a big package nobody has gotten around to figuring out why. Filtering the flags isn't an option because it works for some. Also, this can happen on x86 as well. It's a tricky problem deep in OO.o's build.

How exactly do you have a special CFLAG line set for only openoffice? This would be really helpful to me... Thank you._________________Anyone who is not confused by quantum theory does not truly understand it.

Setting some special CFLAGS is indeed useful, it become possible about 6 months ago I think.
Anyway you can set FLAGS (C, CXX, LD and may be other stuff) for any package you want.
Under /etc/portage/ create a "env" directory. If you want to set particular CFLAGS for openoffice
which is in portage as "app-office/openoffice", under /etc/portage/env create a new directory
called app-office, move in this directory, create a file called "openoffice" and its content should
be as follow:

Code:

CFLAGS="the flags that I want"
CXXFLAGS="some other flags"

and so on if you want LDFLAGS as well.
That's all, you are done, next time you emerge OOo those flags will be used.
One more nice thing, it can be made version specific (openoffice-2.2.1-r1 for example).

If you can tell me exactly which gcc flag is causing the trouble, then we can do something about it, but unfortunately since it's such a big package nobody has gotten around to figuring out why. Filtering the flags isn't an option because it works for some. Also, this can happen on x86 as well. It's a tricky problem deep in OO.o's build.

If you can tell me exactly which gcc flag is causing the trouble, then we can do something about it, but unfortunately since it's such a big package nobody has gotten around to figuring out why. Filtering the flags isn't an option because it works for some. Also, this can happen on x86 as well. It's a tricky problem deep in OO.o's build.

I had the exact same flags as in his first set and the exact same problem; then changed to the exact same as in the second set and succeeded. So, we now know several sets of flags, any of which will succeed:

ERROR: app-office/openoffice-2.2.1 failed.
Call stack:
ebuild.sh, line 1654: Called dyn_install
ebuild.sh, line 1089: Called qa_call 'src_install'
ebuild.sh, line 44: Called src_install
openoffice-2.2.1.ebuild, line 334: Called die
Installation failed!
If you need support, post the topmost build error, and the call stack if relevant.
A complete build log is located at '/var/tmp/portage/app-office/openoffice-2.2.1/temp/build.log'.

!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="." JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info

what does it mean ?

i see openoffice.2.3.0, but i know it has issues with libraries that should be downgraded ...
last time i compiled openoffice i got success with the 2.0.x version, and today it is not in the /usr/portages/* ebuilds

has somebody sucessfully emerged the 2.2.1 ?
if so, could show me how ?