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

Bug 53737

Summary: db-1.85-r1 fails to compile
Product: Gentoo Linux Reporter: Tim Tsahayev <xeonium>
Component: [OLD] Core systemAssignee: Robin Johnson <robbat2>
Status: RESOLVED WORKSFORME    
Severity: normal CC: pauldv
Priority: High    
Version: 2004.1   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Tim Tsahayev 2004-06-12 12:37:07 UTC
While trying to emerge system on a fresh installation db-1.85-r1 build fails.


Reproducible: Always
Steps to Reproduce:
1.emerge system
2.
3.

Actual Results:  
gcc -c -D__DBINTERFACE_PRIVATE -pipe -fomit-frame-pointer -I. -Iinclude 
-I../../hash -g -o hash.o ../../hash/hash.c 
gcc -c -D__DBINTERFACE_PRIVATE -pipe -fomit-frame-pointer -I. -Iinclude 
-I../../hash -g -o hash_bigkey.o ../../hash/hash_bigkey.c 
gcc: Internal error: Segmentation fault (program as) 
Please submit a full bug report. 
See <URL:http://bugs.gentoo.org/> for instructions. 
make: *** [hash_bigkey.o] Error 1 
make: *** Waiting for unfinished jobs.... 
cc1: Broken pipe: error writing to - 
gcc: Internal error: Segmentation fault (program as) 
Please submit a full bug report. 
See <URL:http://bugs.gentoo.org/> for instructions. 
make: *** [hash.o] Error 1 
 
!!! ERROR: sys-libs/db-1.85-r1 failed. 
!!! Function src_compile, Line 28, Exitcode 2 
!!! (no error message) 

Expected Results:  
clean install
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-06-12 17:34:40 UTC
i'd blame your hardware.
reducing your cflags would be a possible workaround.
go run memtest from the livecd, and also cpuburn.

include your 'emerge info' output as well if you still can't find it.
Comment 2 Paul de Vrieze (RETIRED) gentoo-dev 2004-06-13 00:51:26 UTC
Look at bug #20600, there don't seem to be any bad CFLAGS
Comment 3 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-08-30 12:48:21 UTC
binutils on your system is the location of the segfault.
Given the lack of response, please re-open if this still an issue.