Upgrading to avoid the GLSA 200501-33: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-db/mysql-4.0.22-r2" Reproducible: Always Steps to Reproduce: 1. # emerge --sync 2. # emerge --ask --oneshot --verbose ">=dev-db/mysql-4.0.22-r2" 3. Actual Results: if g++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr\"" -DDATADIR="\"/var/lib/mysql\"" -DSHAREDIR="\"/usr/share/mysql\"" -DHAVE_CONFIG_H -I. -I. -I.. -I../bdb/build_unix -I./../include -I./../regex -I. -I../include -I. -O3 -DDBUG_OFF -O2 -mcpu=i686 -fomit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti -fno-implicit-templates -fno-exceptions -fno-rtti -MT item_cmpfunc.o -MD -MP -MF ".deps/item_cmpfunc.Tpo" \ -c -o item_cmpfunc.o `test -f 'item_cmpfunc.cc' || echo './'`item_cmpfunc.cc; \ then mv -f ".deps/item_cmpfunc.Tpo" ".deps/item_cmpfunc.Po"; \ else rm -f ".deps/item_cmpfunc.Tpo"; exit 1; \ fi g++: Internal error: Killed (program cc1plus) Please submit a full bug report. See <URL:http://bugs.gentoo.org/> for instructions. make[4]: *** [item_func.o] Error 1 make[4]: *** Waiting for unfinished jobs.... make[4]: Leaving directory `/var/tmp/portage/mysql-4.0.22-r2/work/mysql-4.0.22/sql' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/mysql-4.0.22-r2/work/mysql-4.0.22/sql' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/tmp/portage/mysql-4.0.22-r2/work/mysql-4.0.22/sql' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/mysql-4.0.22-r2/work/mysql-4.0.22' make: *** [all] Error 2 !!! ERROR: dev-db/mysql-4.0.22-r2 failed. !!! Function src_compile, Line 197, Exitcode 2 !!! compile problem !!! If you need support, post the topmost build error, NOT this status message. Expected Results: It should of successfully built mysql-4.0.22-r2 Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.3, glibc-2.3.4.20040808-r1, 2.4.26 i686) ================================================================= System uname: 2.4.26 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 16 2005, 09:35:02)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.6.3, 1.8.5-r3, 1.7.9-r1, 1.4_p6, 1.9.4 sys-devel/binutils: 2.14.90.0.8-r1 sys-devel/libtool: 1.4.3-r4 virtual/os-headers: 2.4.21-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/alias /var/qmail/control /var/vpopmail/domains /var/vpopmail/etc" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://gentoo.llarian.net/pub/gentoo http://gentoo.llarian.net/ http://cudlug.cudenver.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 apache berkdb crypt curl emboss encode f77 font-server fortran gdbm gpm hardenedphp imap ipv6 libg++ libwww maildir mysql ncurses nls pam perl php python readline slang spell ssl svga tcpd truetype-fonts type1-fonts zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
does it fails in the same line, if you compile again? Internal compiler errors are most often a sign of broken hardware (bad ram, overheating box,...)
yes it always fails in the same line !!! ERROR: dev-db/mysql-4.0.22-r2 failed. !!! Function src_compile, Line 197, Exitcode 2 !!! compile problem I compile other programs with any trouble. This is an email server and has alway been very reliable and stable. No noticed hardware problems.
I meant to say... I compile other programs with out any trouble.
These are some existing bugs with the same internal error from GCC. 83796, 75506, 74319, 63690, 52633, 52314, 51681, 50323, 46880, 44658 I've always managed to trace it down to hardware problems (sometimes very subtle ones). *** This bug has been marked as a duplicate of 20600 ***