oppen office help

[dyerotic]

i just recently installed gentoo. and i tried to emerge openoffice and got this error

Building project psprint
=============
/var/tmp/portage/app-office/openoffice-2.3.1-r1/work/ooo/build/OOG680_m9/psprint/inc
mkout -- version: 1.7
-------------
/var/tmp/portage/app-office/openoffice-2.3.1-r1/work/ooo/build/OOG680_m9/psprint/source/fontmanager
Package gdk-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gdk-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gdk-2.0' found
dmake: Error code 1, while making 'Shell escape'
---* RULES.MK *---

ERROR: Error 65280 occurred while making /var/tmp/portage/app-office/openoffice-2.3.1-r1/work/ooo/build/OOG680_m9/psprint/source/fontmanager
make: *** [stamp/build] Error 1
*
* ERROR: app-office/openoffice-2.3.1-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 5318: Called die
* The specific snippet of code:
* make || die "Build failed"
* The die message:
* Build 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.3.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-office/openoffice-2.3.1-r1/temp/environment'.
*
!!! 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

* Messages for package app-admin/python-updater-0.2:

* This package will overwrite one or more files that may belong to other
* packages (see list below). Add "collision-protect" to FEATURES in
* make.conf if you would like the merge to abort in cases like this. You
* can use a command such as `portageq owners / <filename>` to identify
* the installed package that owns a file. If portageq reports that only
* one package owns a file then do NOT file a bug report. A bug report is
* only useful if it identifies at least two or more packages that are
* known to install the same file(s). If a collision occurs and you can
* not explain where the file came from then you should simply ignore the
* collision since there is not enough information to determine if a real
* problem exists. Please do NOT file a bug report at
* https://bugs.gentoo.org unless you report exactly which two packages
* install the same file(s). Once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/sbin/python-updater

* Messages for package app-text/hunspell-1.1.9:

* To use this package you will also need a dictionary.
* Hunspell uses myspell format dictionaries; find them
* in the app-dicts category as myspell-<LANG>.

* Messages for package net-misc/mDNSResponder-107.6-r5:

* To enable multicast dns lookups for applications
* that are not multicast dns aware, edit the 'hosts:'
* line in /etc/nsswitch.conf to include 'mdns', e.g.:
* hosts: files mdns dns

* Messages for package dev-lang/python-2.4.4-r6:

*
* If you have just upgraded from an older version of python you
* will need to run:
*
* /usr/sbin/python-updater
*
* This will automatically rebuild all the python dependent modules
* to run with python-2.4.
*
* Your original Python is still installed and can be accessed via
* /usr/bin/python2.x.
*

* Messages for package dev-lang/python-2.4.3-r4:

* Unable to establish /usr/share/man/man1/python.1.gz symlink

* Messages for package dev-libs/boost-1.34.1-r2:

* Using the following options to build:
* release debug-symbols=none optimization=none --user-config=/var/tmp/portage/dev-libs/boost-1.34.1-r2/work/boost_1_34_1/user-config.jam

* Messages for package kde-base/kdelibs-3.5.8-r3:

* On some setups, which rely on the correct update of utmp records, not using
* utempter might not update them correctly. If you experience unexpected
* behaviour, try to rebuild kde-base/kdelibs with utempter use-flag enabled.
* QA: stop using the bindnow-flags function ... simply drop it from your ebuild

* Messages for package app-office/openoffice-2.3.1-r1:

*
* It is important to note that OpenOffice.org is a very fragile
* build when it comes to CFLAGS. A number of flags have already
* been filtered out. If you experience difficulty merging this
* package and use agressive CFLAGS, lower the CFLAGS and try to
* merge again. Also note that building OOo takes a lot of time and
* hardware ressources: 4-6 GB free diskspace and 256 MB RAM are
* the minimum requirements. If you have less, use openoffice-bin
* instead.
*
*
* To get a localized build, set the according LINGUAS variable(s).
*
* You are building with java-support disabled, this results in some
* of the OpenOffice.org functionality (i.e. help) being disabled.
* If something you need does not work for you, rebuild with
* java in your USE-flags.
*
*
* ERROR: app-office/openoffice-2.3.1-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 5318: Called die
* The specific snippet of code:
* make || die "Build failed"
* The die message:
* Build 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.3.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-office/openoffice-2.3.1-r1/temp/environment'.
*
* Regenerating GNU info directory index...
* Processed 137 info files.

[schachti]

[dyerotic]

worked, thanks