Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 89221 - update to openoffice-1.1.4-r1 fails
Summary: update to openoffice-1.1.4-r1 fails
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-15 13:51 UTC by Bernd Waibel
Modified: 2005-04-16 14:24 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Waibel 2005-04-15 13:51:09 UTC
Yesterday and today the update to openoffice-1.1.4-r1 fails. Yesterday it couldn't find a header file 'tree*.hxx' (don't remember the exact name, sorry), so I decided to wait a day and try again. Today it produces a different error ):

Making: ../../unxlngi4.pro/lib/svcontnr.lib
echo unxlngi4.pro/obj/svtabbx.o unxlngi4.pro/obj/svicnvw.o unxlngi4.pro/obj/svimpicn.o unxlngi4.pro/obj/treelist.o unxlngi4.pro/obj/svlbox.o unxlngi4.pro/obj/svimpbox.o unxlngi4.pro/obj/svlbitm.o unxlngi4.pro/obj/svtreebx.o | xargs -n1 > ../../unxlngi4.pro/lib/svcontnr.lib
------------------------------
Making: ../../unxlngi4.pro/slb/svcontnr.lib
echo unxlngi4.pro/slo/svtabbx.o unxlngi4.pro/slo/svicnvw.o unxlngi4.pro/slo/svimpicn.o unxlngi4.pro/slo/treelist.o unxlngi4.pro/slo/svlbox.o unxlngi4.pro/slo/svimpbox.o unxlngi4.pro/slo/svlbitm.o unxlngi4.pro/slo/svtreebx.o unxlngi4.pro/slo/imivctl1.o unxlngi4.pro/slo/imivctl2.o unxlngi4.pro/slo/ivctrl.o unxlngi4.pro/slo/fileview.o unxlngi4.pro/slo/templwin.o unxlngi4.pro/slo/tooltiplbox.o | xargs -n1 > ../../unxlngi4.pro/slb/svcontnr.lib
dmake:  Error -- `./fileview.hrc' not found, and can't be made
---* TG_SLO.MK *---

ERROR: Error 65280 occurred while making /mnt/tmp/portage/openoffice-1.1.4-r1/work/svtools/source/contnr

I searched bugzilla, but only found bugs related to release 1.1.4.

The strange thing for me, is the failing at two different points of the compilation, although I didn't change any settings, just did the usual daily system/world update (xterm, qt and bin86 for system update and cl-asdf, common-lisp-controller, webmin and openoffice for the world update today)

My emerge info:
Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-ck4-ipv6m i686)
=================================================================
System uname: 2.6.11-ck4-ipv6m i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 26 2005, 02:29:05)]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.14
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium4 -O2 -fforce-addr -mfpmath=sse -mmmx -msse -msse2 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium4 -O2 -fforce-addr -mfpmath=sse -mmmx -msse -msse2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig buildsyspkg candy ccache collision-protect distlocks fixpackages nostrip sandbox sfperms strict userpriv usersandbox"
GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/mnt/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/local/portage-de"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 X aalib accessibility acl acpi aim alsa apache2 arts avi bash-completion berkdb bitmap-fonts cdr crypt cscope cups curl dedicated doc dvd emboss encode esd exif fam flac foomaticdb fortran freetds gd gdbm ggi gif gnome gpm gstreamer gtk2 hal icq jabber jack java jikes joystick jpeg junit kdeenablefinal libwww linguas_de mad maildir mcal mikmod mmx mmx2 motif mp3 mpeg mpi msn ncurses nls nptl odbc offensive ogg oggvorbis openal opengl oscar pam pic pie png ppds pwdb python qt quicktime readline samba sdl shared slang source spell sqlite sse ssl svg svga sysvipc tcpd tetex tiff truetype truetype-fonts type1-fonts unicode usb videos vorbis xml2 xmms xprint yahoo zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

Did I forget anything?
Comment 1 Andreas Proschofsky (RETIRED) gentoo-dev 2005-04-15 13:57:51 UTC
If it fails at different points this most likely is no problem with OOo but with your hardware. Could it be that your cpu gets too hot? Or that you run out of diskspace / memory?
Comment 2 Bernd Waibel 2005-04-15 14:39:26 UTC
Don't think that I ran out of memory or disk space. I have 1280 megs of RAM and the partition where I compile portage packages has 12 gig free space after the compilation stopped.
I don't have special sensors, but I don't think the processor gets too hot. It's not overclocked, the case is closed and I never got any error or warning related to overheating the cpu.
I'll do a memtest on the next reboot tomorrow to ensure the memory is not corrupted. I had a distributed computing client (boinc) running on the machine at the same time, but it is configured to use only one of the two virtual processors (I have hyperthreading activated). May this be a problem (although I never had problems with it before. It was running on all the other OOo updates as well)?
Thanks for your lighting fast answer :)
Comment 3 Andreas Proschofsky (RETIRED) gentoo-dev 2005-04-15 14:53:33 UTC
Everything might be a problem if you try to build OOo, it is a very sensible beast ;) But generally, if the build fails at different points, it most likely is not the fault of OOo...
Comment 4 Paul de Vrieze (RETIRED) gentoo-dev 2005-04-16 05:25:58 UTC
Take a look at bug #20600. It gives various probable causes for compilation failure. Good chance you're suffering from one of them.
Comment 5 Bernd Waibel 2005-04-16 14:05:56 UTC
It compiled successfully today. I ran memtest after boot, but it found no errors, after this it compiled. But I didn't run the distributed client at the same time, so processor load might be lower than before. Strange, as something never happens before.

Much thanks for your help and hints to bug 20600 :)
This is solved for me.
Comment 6 Andreas Proschofsky (RETIRED) gentoo-dev 2005-04-16 14:24:11 UTC
Ok, thanks for reporting back, closing this