Bug 60532 – emerge system fails during build of glibc-2.3.3.20040420-r1 on HP Vectra VL5/166 MMX

• Product: Gentoo Linux
• Status: RESOLVED WORKSFORME

[Description Stephen Crawford 2004-08-16 01:51:18 UTC]

When trying to 'emerge system' during a stage 2 install (of both 2004.1 and 2004.2) emerge fails at same location each time. The final output is:



Reproducible: Always
Steps to Reproduce:
1. Follow Gentoo installation manual or Quick Install Reference
2. download and unpack stage 2 tarball
3. download and unpack portage snapshot
4. chroot to /mnt/gentoo
5. emerge system

Actual Results:  
After successfully building first 4/5 packages glibc starts and after a bit the
following output is displayed on screen and emerge stops. Computer will still
take input and will output but if you try to emerge system again then it stops
same place with the same error listing--

__alloc_pages: 0-order allocation filed (gfp=0xf0/0)
__alloc_pages: 0-order allocation filed (gfp=0x1d2/0)
__alloc_pages: 0-order allocation filed (gfp=0x1d2/0)
VM: killing process cc1
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions
make[2]:
***[/var/tmp/portage/glibc-2.3.3.20040420-r1/work/glibc-2.3.2/buildhere/iconvdata/euc-jp.ox]
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-libc/glibc-2.3.3.20040420-r1 failed.
!!! Function src_compile, Line 585, Exitcode 2
!!! (no error message)

Expected Results:  
Finished emerge of system

Portage 2.0.50-r5 (default-x86-2004.0, gcc-3.3.2,
glibc-2.3.3.20040420-r0,2,3,2-r9, 2.4.24-xfs-r3)
====================================================================
System uname: 2.4.24-xfs-r3 i586 Pentium MMX
Gentoo Base System version 1.4.3.13
Autoconf:
Automake:
ACCEPT_KEYWORD="X86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mcpu=pentium-mmx -march=pentium-mmx -fomit-frame-pointer"
CHOST="i386-pc-linux-gnu"
COMPILER="gcc"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CXXFLAGES="-O2 -mcpu=pentium-mmx -march=pentium-mmx -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
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="apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gnome gpm gtk2 im
lib ipv6 jpeg 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 xm12 xmms xv zlib"

[Comment 1 SpanKY 2004-08-17 20:21:23 UTC]

__alloc_pages: 0-order allocation filed (gfp=0xf0/0)
__alloc_pages: 0-order allocation filed (gfp=0x1d2/0)
__alloc_pages: 0-order allocation filed (gfp=0x1d2/0)
VM: killing process cc1

that looks like the kernel doing it


CFLAGS="-O2 -mcpu=pentium-mmx -march=pentium-mmx -fomit-frame-pointer"
CHOST="i386-pc-linux-gnu"

that is easily an unstable situation

i'd review both these problems and try again