Summary: | OpenOffice 2.0.0 build error (recovery-report.diff: testing:..No such file or directory) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maik Hinrichs <maik> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maik Hinrichs
2005-12-02 05:43:16 UTC
Uhm, are you *really* sure there's enough disk space? Yes, there is 21GB free storage in /var This is the first error: `/var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.1' cp -f /usr/portage/distfiles/libwpd-0*.tar.gz /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.1/build/OOO_2_0_0/libwpd/download/ || echo "cannot copy libwpd" cp: cannot create regular file There is not a dir OOO_2_0_0, there is only a dir ooo680-m3. There is something seriously going wrong here (actually there are two many things going wrong here to easily find what the culprit is ;) ). Are you sure, you did not change the ebuild or have another one in your overlay? Also: Have the digests been correct from the start or did you redo them? Cause it looks like the source is actually never unpacked. Also the necessary dirs are not created and so on. Do you use a modified portage in some way? I did not change portage und ebuild both and have not overlays. After removing build dir I get same result/error. # rm -rf /var/tmp/portage/openoffice-2.0.0/ # emerge openoffice Calculating dependencies ...done! >>> emerge (1 of 1) app-office/openoffice-2.0.0 to / >>> md5 files ;-) openoffice-1.1.4-r1.ebuild >>> md5 files ;-) openoffice-1.1.5.ebuild >>> md5 files ;-) openoffice-2.0.0.ebuild >>> md5 files ;-) files/digest-openoffice-1.1.4-r1 >>> md5 files ;-) files/digest-openoffice-1.1.5 >>> md5 files ;-) files/digest-openoffice-2.0.0 >>> md5 files ;-) files/1.1.4/gcc34.patch.bz2 >>> md5 files ;-) files/1.1.4/pyunolink-fix.patch >>> md5 files ;-) files/1.1.4/ooffice-wrapper-1.3 >>> md5 files ;-) files/1.1.4/gcc-instlib.patch >>> md5 files ;-) files/1.1.4/openoffice-java.patch >>> md5 files ;-) files/1.1.4/javafix.patch >>> md5 files ;-) files/1.1.4/hardened-link.patch >>> md5 files ;-) files/1.1.4/gcc34-nojava-fix.patch >>> md5 files ;-) files/1.1.4/pthreadlink-fix.patch >>> md5 files ;-) files/1.1.4/freetype-217.patch >>> md5 files ;-) files/1.1.4/nptl.patch >>> md5 files ;-) files/1.1.4/gcc34-sal-link-to-libsupc++.diff >>> md5 files ;-) files/1.1.4/STLport-vector.patch >>> md5 files ;-) files/1.1.4/newstlportfix.patch >>> md5 files ;-) files/1.1.4/getcompver.awk.patch >>> md5 files ;-) files/1.1.4/cws-heapbug_CAN-2005-0941.diff >>> md5 files ;-) files/1.1.4/build-new-xslt.diff >>> md5 files ;-) files/1.1.5/gcc34-nojava-fix.patch >>> md5 files ;-) files/1.1.5/STLport-vector.patch >>> md5 files ;-) files/1.1.5/freetype-217.patch >>> md5 files ;-) files/1.1.5/gcc-instlib.patch >>> md5 files ;-) files/1.1.5/ooffice-wrapper-1.3 >>> md5 files ;-) files/1.1.5/nptl.patch >>> md5 files ;-) files/1.1.5/gcc34-sal-link-to-libsupc++.diff >>> md5 files ;-) files/1.1.5/gcc34.patch.bz2 >>> md5 files ;-) files/1.1.5/getcompver.awk.patch >>> md5 files ;-) files/1.1.5/hardened-link.patch >>> md5 files ;-) files/1.1.5/javafix.patch >>> md5 files ;-) files/1.1.5/newstlportfix.patch >>> md5 files ;-) files/1.1.5/openoffice-java.patch >>> md5 files ;-) files/1.1.5/pthreadlink-fix.patch >>> md5 files ;-) files/1.1.5/pyunolink-fix.patch >>> md5 files ;-) files/1.1.5/build-new-xslt.diff >>> md5 src_uri ;-) OOO_2_0_0-core.tar.bz2 >>> md5 src_uri ;-) OOO_2_0_0-system.tar.bz2 >>> md5 src_uri ;-) OOO_2_0_0-lang.tar.bz2 >>> md5 src_uri ;-) ooo-build-2.0.0.2.tar.gz >>> md5 src_uri ;-) libwpd-0.8.3.tar.gz >>> md5 src_uri ;-) ooo_crystal_images-6.tar.bz2 >>> md5 src_uri ;-) extras-2.tar.bz2 * * 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. * >>> Unpacking source... >>> Unpacking ooo-build-2.0.0.2.tar.gz to /var/tmp/portage/openoffice-2.0.0/work >>> Source unpacked. checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for perl... /usr/bin/perl checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for FOO_COMMON... yes checking for FOO_OPTIONAL... yes found OOO_2_0_0, using /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.2/patches/OOO_2_0/apply checking for directory where to download sources ... /usr/portage/distfiles checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... none checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking security/pam_appl.h usability... yes checking security/pam_appl.h presence... yes checking for security/pam_appl.h... yes checking png.h usability... yes checking png.h presence... yes checking for png.h... yes checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for autoconf... yes checking for flex... yes checking for bison... yes checking for ccache... no checking for widget sets... checking for FOO_GTK... yes --enable-gtk --enable-kde checking whether Hunspell UNO is enabled... no checking for libhunspell... no needed checking for broken aliases... ok checking for Open Clip Art Library... no checking for ooo-version... 2.0 checking for binsuffix... 2 checking for requested localizations... de en-US checking whether to enable Mono bindings... no checking whether to enable Access import... no checking whether to enable debugging code... configure: creating ./config.status config.status: creating download config.status: creating scratch/place config.status: creating intltool-extract config.status: creating intltool-merge config.status: creating intltool-update config.status: creating Makefile config.status: creating ooo1.1.spec config.status: creating bin/setup config.status: creating bin/Makefile config.status: creating desktop/Makefile config.status: creating distro-configs/Makefile config.status: creating distro-configs/Ark.conf config.status: creating distro-configs/Common.conf config.status: creating distro-configs/Debian.conf config.status: creating distro-configs/DebianSarge.conf config.status: creating distro-configs/Debian64.conf config.status: creating distro-configs/Ubuntu.conf config.status: creating distro-configs/Ubuntu64.conf config.status: creating distro-configs/NLD.conf config.status: creating distro-configs/NLD64.conf config.status: creating distro-configs/SUSE.conf config.status: creating distro-configs/Mandriva.conf config.status: creating distro-configs/Mandriva64.conf config.status: creating distro-configs/Gentoo.conf config.status: creating distro-configs/QiLinux.conf config.status: creating distro-configs/Frugalware.conf config.status: creating distro-configs/Frugalware64.conf config.status: creating fonts/Makefile config.status: creating patches/Makefile config.status: creating patches/a11y/Makefile config.status: creating patches/cairo/Makefile config.status: creating patches/evo2/Makefile config.status: creating patches/vba/Makefile config.status: creating patches/mono/Makefile config.status: creating patches/src680/Makefile config.status: creating patches/OOO_2_0/Makefile config.status: creating patches/64bit/Makefile config.status: creating po/Makefile config.status: creating doc/Makefile config.status: creating src/Makefile config.status: creating stamp/Makefile config.status: creating man/Makefile config.status: creating www/Makefile config.status: creating www/images/Makefile config.status: creating www/tinder-scripts/Makefile config.status: executing depfiles commands Building openoffice tag: OOO_2_0_0 apply rules: /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.2/patches/OOO_2_0/apply build dir: /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.2/build/OOO_2_0_0 tools dir: /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.2 src package dir: /usr/portage/distfiles distro: Gentoo widget sets: gtk kde icons: industrial crystal hicontrast gcc to use: from system hunspell-uno: no hunspell-lib: no needed openclipart: no mono bindings: no mdbtools/access: no java: yes ooo-install-dir: openoffice force gcc33: no ccache: no icecream: no cairo: no build type: product build download mirror: http://go-ooo.org/packages To build run: ./download make bin/ooinstall <path-to-install> This is ooo-build-2-0 - the stable branch for 2.0 release. If you want to build something cool, unstable, and risky, use HEAD. * Building OpenOffice.org... /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.2/bin/transform --revert /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.2 /var/tmp/portage/openoffice-2.0.0/work/ooo-build-2.0.0.2/build/OOO_2_0_0 Making all in po ... It seems to be a race condition of some sort. Do things work when you use MAKEOPTS="" emerge openoffice Yes!! I compiled it successfully using MAKEOPTS="". Thanks, Maik thanks for reporting back, closing |