Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 50907

Summary: openoffice 1.1.1-r1 emerge-ing ends up with segfault during dmake of jdbc driver
Product: Gentoo Linux Reporter: Stefano David <sdavid>
Component: New packagesAssignee: Gentoo Office Team <office>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge info

Description Stefano David 2004-05-13 01:12:07 UTC
While emerging OO 1.1.1-r1, I get following message:

/var/tmp/portage/openoffice-1.1.1-r1/work/oo_1.1.1_src/connectivity/source/drivers/jdbc/Statement.cxx:
In member function `virtual cppu::IPropertyArrayHelper*
connectivity::java_sql_Statement_Base::createArrayHelper() const':
/var/tmp/portage/openoffice-1.1.1-r1/work/oo_1.1.1_src/connectivity/source/drivers/jdbc/Statement.cxx:918:
internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
The bug is not reproduceable, so it is likely a hardware or OS problem
dmake:  Error code 1, while making
'../../../unxlngi4.pro/slo/Statement.obj'
---* TG_SLO.MK *---
 
ERROR: Error 65280 occurred while making
/var/tmp/portage/openoffice-1.1.1-r1/work/oo_1.1.1_src/connectivity/source/drivers/jdbc
 
!!! ERROR: app-office/openoffice-1.1.1-r1 failed.
!!! Function src_compile, Line 365, Exitcode 1
!!! Build failed!



Reproducible: Couldn't Reproduce
Steps to Reproduce:
As shown above, this behavior is not reproduceable.



Expected Results:  
Successful emerge of Openoffice

I emerged OO right after gnome. the only other program running was irssi. My PC
is an athlon XP 1700+ with 256Mb RAM
Comment 1 Stefano David 2004-05-13 01:12:50 UTC
Created attachment 31313 [details]
emerge info
Comment 2 Paul de Vrieze (RETIRED) gentoo-dev 2004-05-13 03:08:50 UTC
Probably you have hardware problems. Take a look at bug #20600

*** This bug has been marked as a duplicate of 20600 ***