Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 81464 - emerge stops with an error when updating openoffice to version 1.1.4
Summary: emerge stops with an error when updating openoffice to version 1.1.4
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Office Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-10 01:00 UTC by Björn Kuhlmann
Modified: 2005-04-24 13:46 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 Björn Kuhlmann 2005-02-10 01:00:51 UTC
1. emerge sync
2. emerge -vauD openoffice
3.
[many other things]
=============
Building project udkapi
=============
/var/tmp/portage/openoffice-1.1.4/work/udkapi/com/sun/star/corba/giop
mkout -- version: 1.3
idlc @/var/tmp/portage/openoffice-1.1.4/temp/mksKgXqn
idlc: compile 'giop.idl' ...
idlc: returned successful
Sun Microsystems (R) idlc Version 1.0

idlc @/var/tmp/portage/openoffice-1.1.4/temp/mkkyjo4N
idlc: compile 'giop.idl' ...
idlc: returned successful
Sun Microsystems (R) idlc Version 1.0

------------------------------
Making: ../../../../../unxlngi4.pro/misc/cssgiop.dpc
dmake subdmake=true  -f makefile.mk strip="true" product="full" depend=t ALLDPC
Making : Dependencies
rm -f ../../../../../unxlngi4.pro/ucr/cssgiop.db
regmerge ../../../../../unxlngi4.pro/ucr/cssgiop.db UCR @/var/tmp/portage/openoffice-1.1.4/temp/mkGroh7e
dmake:  Error code 255, while making '../../../../../unxlngi4.pro/ucr/cssgiop.db'
dmake:  '../../../../../unxlngi4.pro/ucr/cssgiop.db' removed.
---* TG_SLO.MK *---

ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.1.4/work/udkapi/com/sun/star/corba/giop

!!! ERROR: app-office/openoffice-1.1.4 failed.
!!! Function src_compile, Line 416, Exitcode 1
!!! Build failed!
!!! If you need support, post the topmost build error, NOT this status message.


Reproducible: Always
Steps to Reproduce:
1. emerge sync
2. emerge -vauD openoffice




Expected Results:  
Should install without an error
Comment 1 Paul de Vrieze (RETIRED) gentoo-dev 2005-02-11 02:27:58 UTC
Could you please attach a full build log, it's impossible to diagnose what goes wrong based on this snippet. Could you also post the output of "emerge info"
Comment 2 John Heinig 2005-03-09 22:08:15 UTC
java -classpath /var/tmp/portage/openoffice-1.1.4/work/solver/645/unxlngi4.pro/bin/xt.jar:/var/tmp/portage/openoffice-1.1.4/work/solver/645/unxlngi4.pro/bin/parser.jar -Dcom.jclark.xsl.sax.parser=com.sun.xml.parser.Parser com.jclark.xsl.sax.Driver org/openoffice/Inet.xcs ../../util/schema_val.xsl ../../unxlngi4.pro/misc/registry/schema/org/openoffice/Inet.val file=org/openoffice/Inet pathSeparator=/
Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - no /proc/self/stat
file:/var/tmp/portage/openoffice-1.1.4/work/officecfg/registry/schema/org/openoffice/Inet.xcs:1: CHECKING CONSISTENCY ...
java -classpath /var/tmp/portage/openoffice-1.1.4/work/solver/645/unxlngi4.pro/bin/xt.jar:/var/tmp/portage/openoffice-1.1.4/work/solver/645/unxlngi4.pro/bin/parser.jar -Dcom.jclark.xsl.sax.parser=com.sun.xml.parser.Parser com.jclark.xsl.sax.Driver org/openoffice/Inet.xcs ../../util/sanity.xsl ../../unxlngi4.pro/misc/registry/schema/org/openoffice/Inet.san file=org/openoffice/Inet pathSeparator=/
Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - no /proc/self/stat
java -classpath /var/tmp/portage/openoffice-1.1.4/work/solver/645/unxlngi4.pro/bin/xt.jar:/var/tmp/portage/openoffice-1.1.4/work/solver/645/unxlngi4.pro/bin/parser.jar -Dcom.jclark.xsl.sax.parser=com.sun.xml.parser.Parser com.jclark.xsl.sax.Driver org/openoffice/Inet.xcs ../../util/schema_trim.xsl ../../unxlngi4.pro/misc/registry/schema/org/openoffice/Inet.tmp
Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - no /proc/self/stat
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://www.blackdown.org/cgi-bin/jdk
#
# Java VM: Java HotSpot(TM) Client VM (Blackdown-1.4.2-01 mixed mode)
#
# Error ID: 4F533F4C494E55583F491418160E4350500359
#

Heap at VM Abort:
Heap
 def new generation   total 576K, used 121K [0xaba70000, 0xabb10000, 0xabf50000)  eden space 512K,  11% used [0xaba70000, 0xaba7e7c8, 0xabaf0000)
  from space 64K, 100% used [0xabaf0000, 0xabb00000, 0xabb00000)
  to   space 64K,   0% used [0xabb00000, 0xabb00000, 0xabb10000)
 tenured generation   total 1408K, used 1013K [0xabf50000, 0xac0b0000, 0xafa70000)
   the space 1408K,  71% used [0xabf50000, 0xac04d4b0, 0xac04d600, 0xac0b0000)
 compacting perm gen  total 4096K, used 2213K [0xafa70000, 0xafe70000, 0xb3a70000)
   the space 4096K,  54% used [0xafa70000, 0xafc997d0, 0xafc99800, 0xafe70000)
Abort
dmake:  Error code 134, while making '../../unxlngi4.pro/misc/registry/schema/org/openoffice/Inet.xcs'
---* TG_SLO.MK *---

ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-1.1.4/work/officecfg/registry/schema

!!! ERROR: app-office/openoffice-1.1.4 failed.
!!! Function src_compile, Line 416, Exitcode 1
!!! Build failed!
!!! If you need support, post the topmost build error, NOT this status message.
Comment 3 John Heinig 2005-03-09 22:09:48 UTC
I had the same problem, so here's the rest of my info.

ranthog / # emerge info
Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r6 i686)
=================================================================
System uname: 2.6.10-gentoo-r6 i686
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar  6 2005, 23:54:45)]
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-r1
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -O3 -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks fixpackages sandbox sfperms"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowex X aim alsa apm avi berkdb bitmap-fonts cdr cjk crypt cups curl doc dvd emboss encode esd fam font-server foomaticdb fortran ftp gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 jabber java jpeg kerberos libg++ libwww mad maildir mbox mikmod mmx motif mozilla mp3 mpeg ncurses nls nptl offensive oggvorbis opengl pam pda pdflib perl png python quicktime readline real samba sdl spell sse ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts usb wmf xine xml2 xmms xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Comment 4 Paul de Vrieze (RETIRED) gentoo-dev 2005-03-10 03:10:19 UTC
It's a know bug in some of the blackdown jdks. Try upgrading your jdk or use a different one.
Comment 5 Kevin F. Quinn (RETIRED) gentoo-dev 2005-04-24 12:04:28 UTC
I get the same error from the JVM trying to build libidn-0.5.13, as well as openoffice-1.1.4-r1; for me the error with openoffice occurs at a different place, but the JVM error is the same.  Since this is not Openoffice-specific, perhaps it would be useful to reassign and/or cc to the Java herd.

Same error with Blackdown-1.4.2-01 (from dev-java/blackdown-jdk-1.4.2.01-r2) and Sun 1.4.2_08-b03 (from dev-java/sun-jdk-1.4.2.08)

Sun jdk error id: 4F533F4C494E55583F491418160E4350500351
Blackdown jdk error id: 4F533F4C494E55583F491418160E4350500359

Paul - could you post a reference to the known bug you mentioned?  I couldn't find anything for those error IDs in either the Blackdown bug database at http://www.blackdown.org/cgi-bin/jdk or the Sun database at http://java.sun.com/cgi-bin/bugreport.cgi.
Comment 6 Paul de Vrieze (RETIRED) gentoo-dev 2005-04-24 13:46:50 UTC
Kevin, I'm sorry but I don't have bug ID's. It's more of an observation. Java should not generate Internal Errors, and I've seen this before.