Bug 60884 – glibc-2.3.3.20040420-r1 compilation fails on Athlon XP 2400+

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Alain Hugentobler 2004-08-19 05:04:52 UTC]

When progressing from Stage2 to Stage3, the compilation of glibc-2.3.3.20040420-r1 fails, and it is reproductible on my Athlon XP 2400+ system. Here are the messages I get :

gcc gbgbk.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -freorder-blocks -march=athlon-xp -mpreferred-stack-boundary=2  -fPIC    -I../include -I. -I/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata -I.. -I../libio  -I/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386 -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/include -isystem /usr/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h  -DPIC -DSHARED     -DNOT_IN_libc -o /var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata/gbgbk.os -MD -MP -MF /var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata/gbgbk.os.dt
In file included from gbk.c:13486:
../iconv/skeleton.c: In function `gconv':
../iconv/skeleton.c:801: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
gcc iso-2022-cn.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings -freorder-blocks -march=athlon-xp -mpreferred-stack-boundary=2  -fPIC    -I../include -I. -I/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata -I.. -I../libio  -I/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere -I../sysdeps/i386/elf -I../linuxthreads/sysdeps/unix/sysv/linux/i386 -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386 -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386 -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/include -isystem /usr/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h  -DPIC -DSHARED     -DNOT_IN_libc -o /var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata/iso-2022-cn.os -MD -MP -MF /var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata/iso-2022-cn.os.dt
The bug is not reproducible, so it is likely a hardware or OS problem.
make[2]: *** [/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata/gbk.os] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/iconvdata'
make[1]: *** [iconvdata/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2'
make: *** [all] Error 2
 
!!! ERROR: sys-libs/glibc-2.3.3.20040420-r1 failed.
!!! Function src_compile, Line 585, Exitcode 2
!!! (no error message)


Reproducible: Always
Steps to Reproduce:
1. Progressing from Stage2 to Stage3
2. emerge system
3.

Actual Results:  
make: *** [all] Error 2
 
!!! ERROR: sys-libs/glibc-2.3.3.20040420-r1 failed.
!!! Function src_compile, Line 585, Exitcode 2
!!! (no error message)


Expected Results:  
compiled glibc

Portage 2.0.50-r9 (default-x86-2004.2, gcc-3.3.3, glibc-2.3.3.20040420-r0,
2.4.26-gentoo-r6)
=================================================================
System uname: 2.4.26-gentoo-r6 i686 AMD Athlon(TM) XP 2400+
Gentoo Base System version 1.4.16
Autoconf:
Automake:
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo
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="X apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gnome gpm gtk
gtk2 imlib jpeg kde libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis
opengl oss pam pdflib png python qt quicktime readline sdl slang spell ssl svga
tcpd truetype x86 xml2 xmms xv zlib"

[Comment 1 Martin Holzer (RETIRED) 2004-08-19 05:20:39 UTC]

do you have enough ram ?
did you aktivate swap ?

[Comment 2 Alain Hugentobler 2004-08-19 11:02:03 UTC]

Faulty hardware (RAM) caused the problem !
memtest86 was unable to spot it ...

[Comment 3 solar (RETIRED) 2004-08-19 11:16:10 UTC]

Faulty hardware seems to be a reoccurring theme with AMD Athlon users.