Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 140924 - openoffice-2.0.3 build fails on 'project boost'
Summary: openoffice-2.0.3 build fails on 'project boost'
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2006-07-18 08:27 UTC by Lindsay Haisley
Modified: 2006-07-18 15:01 UTC (History)
0 users

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


Note You need to log in before you can comment on or make changes to this bug.
Description Lindsay Haisley 2006-07-18 08:27:26 UTC
Building project boost

ERROR: Error 11 occurred while making /var/tmp/portage/openoffice-2.0.3/work/ooo-build-
make: *** [stamp/build] Error 1

!!! ERROR: app-office/openoffice-2.0.3 failed.
Call stack:, line 1539:   Called dyn_compile, line 939:   Called src_compile
  openoffice-2.0.3.ebuild, line 251:   Called die

# emerge --info
Portage 2.1-r1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4,glibc-, 2.6.16-gentoo-r9 i686)
System uname: 2.6.16-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz
Gentoo Base System version 1.6.15
ccache version 2.3 [disabled]
app-admin/eselect-compiler: [Not Present]
dev-lang/python:     2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
CFLAGS="-O2 -march=pentium4 -fprefetch-loop-arrays -pipe"
CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /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/"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-O2 -march=pentium4 -fprefetch-loop-arrays -pipe"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
USE="x86 X Xaw3d acl acpi alsa apache2 apm arts avi berkdb bindist bitmap-fonts bonobo cdr cli crypt cups curl dlloader doc dri dvd dvdr eds emboss encode esd evo fastcgi firefox flash foomaticdb fortran gdbm gif gimp gnome gpm gps gstreamer gtk gtk2 gtkhtml hal imap imlib ipv6 isdnlog java jikes jpeg kde ldap libg++ libwww mad maildir mcal mikmod motif mp3 mpeg mysql ncurses nls nptl ogg oggvorbis opengl oss pam pcre pdflib perl plotutils png ppds pppd python qt qt3 qt4 quicktime readline reflection samba sasl scanner sdl seamonkey session slang slp snmp spell spl sse ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts udev usb vorbis xml xml2 xmms xorg xosd xv zeo zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux userland_GNU"
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-07-18 08:29:58 UTC
Well sorry, but this is not really useful, post more lines above.
Comment 2 Lindsay Haisley 2006-07-18 09:18:12 UTC
Jacub, how much of the build output should I post?  The error occurs  many minutes into a very verbose build.  I've tee'd the output to a file, which has already run to over 4 megs.  I can attach the whole thing, or a portion of it.  This is a damned complex build and takes many hours.  I'm not sure how many minutes or hours into the build (which ran overnight) the failure occurred, or how big this file will eventually become.  Let me know and I'll post what's needed.

Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-07-18 09:54:05 UTC
Well, just some 20 lines above or so, or attach the part of the log with the error here, but we really need some context.
Comment 4 Lindsay Haisley 2006-07-18 10:13:14 UTC
If it fails again I'll do this, but it's about 1.5 hours into the build and still on track.  Grepping the build output file indicates that it's already successfully passed "Building project boost", and so unless it fails somewhere else, or it returns to this build segment and fails, it may go to completion and we can close this bug altogether <knocking on wood!>.  This smells like resource exhaustion.  I know that the OO build has a reputation as a resource hog.
Comment 5 Lindsay Haisley 2006-07-18 15:01:16 UTC
The OO emerge went through to the end this time - all 5 hours of it :-)  Since the error isn't reproduceable (my guess is that it represented a segfault caused by resource depletion) I'm closing it altogether.