Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 28176 - emerge octave failed at gendoc.cc with internal error (gcc 3.2.3)
Summary: emerge octave failed at gendoc.cc with internal error (gcc 3.2.3)
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: George Shapovalov (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-08 04:11 UTC by Fauzie Wiriadisastra
Modified: 2003-09-09 20:22 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 Fauzie Wiriadisastra 2003-09-08 04:11:03 UTC
emerging octave (v2.1.49) terminates due to gcc internal error at gendoc.cc 

Reproducible: Always
Steps to Reproduce:
1. emerge octave 
Actual Results:  
making gendoc.cc 
g++ -O3 -march=i686 -o gendoc gendoc.cc -lz 
gendoc.cc: In function `int main()': 
gendoc.cc:987: internal error: Segmentation fault 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://bugs.gentoo.org/> for instructions. 
make[4]: *** [gendoc] Error 1 
make[4]: Leaving directory `/var/tmp/portage/octave-2.1.49/work/octave-2.1.49/src' 
make[3]: *** [src-DOCSTRINGS] Error 2 
make[3]: Leaving directory 
`/var/tmp/portage/octave-2.1.49/work/octave-2.1.49/doc/interpreter' 
make[2]: *** [interpreter] Error 2 
make[2]: Leaving directory `/var/tmp/portage/octave-2.1.49/work/octave-2.1.49/doc' 
make[1]: *** [doc] Error 2 
make[1]: Leaving directory `/var/tmp/portage/octave-2.1.49/work/octave-2.1.49' 
make: *** [all] Error 2 
 
!!! ERROR: app-sci/octave-2.1.49 failed. 
!!! Function src_compile, Line 46, Exitcode 2 
!!! emake failed 
 

Expected Results:  
octave installed 

Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r6) 
================================================================= 
System uname: 2.4.20-gentoo-r6 i686 AMD Athlon(tm) Processor 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-O3 -march=i686" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config 
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config 
/usr/share/config" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-O3 -march=i686" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="sandbox ccache" 
GENTOO_MIRRORS="http://gentoo.oregonstate.edu 
http://distro.ibiblio.org/pub/Linux/distributions/gentoo" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg gnome libg++ mad 
mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib 
gtkhtml alsa gdbm berkdb slang readline arts tetex bonobo svga java mysql X sdl gpm 
tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt kde motif opengl mozilla"
Comment 1 George Shapovalov (RETIRED) gentoo-dev 2003-09-08 15:58:22 UTC
Um, internal error?
Try updating the gcc and try again? gcc-3.3.1 just went ~x86, you can try this one..
Also -O3 quite often makes the code larger and slower. You might want to consider "downgrading" your C[XX]FLAGS to -O2.

George
Comment 2 Fauzie Wiriadisastra 2003-09-08 21:19:40 UTC
I would rather wait a litle more before upgrading gcc. For the time being I 
managed to emerge octave 2.1.40, which is enough for what I am doing right 
now. I'll try -O2 if I got some time, just for an experiment.  
Comment 3 George Shapovalov (RETIRED) gentoo-dev 2003-09-09 20:22:07 UTC
Then you can try remerging your current version of gcc. It might have become "slightly" compromised (or more likely some libs might develop conflicts).

And yea, I cannot reproduce this problem - neither with 3.2.3 nor with 3.3.1. I guess I'll have to close this bug with RESOLVED/INVALID for now. Please reopen it if you get anything more specific or if you learn of recurring failures on some other system..

Few last minute thoughts:
1. gcc segfaulting might indicate hardware malfunction (overheating most likely, usually triggered at the point of most intense calculations). You may try emerging this version again and see if this happens at the same point, then cd to the build dir and issue manual make to see if it segfaults right away or performs a bit more compilation..
2. I already mentioned -O3 => -O2 in C[XX]FLAGS. You can try playing with -march as well. Try setting it to athlon, as you have this processor? Or to i586 for just this compilation.

George