Bug 112444 – emerging glibc with -ggdb3 makes portage go boom

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Simon Stelling (RETIRED) 2005-11-13 11:59:45 UTC]

when setting up a fresh 2005.1 stage3 and trying to emerge glibc-2.3.5-r2, it
horribly fails:

>>> /lib64/libnss_nisplus.so.2 -> libnss_nisplus-2.3.5.so
>>> /lib64/libnss_compat.so.2 -> libnss_compat-2.3.5.so
>>> /lib64/libutil.so.1 -> libutil-2.3.5.so
!!! FAILED postinst: 2816

Heuristic told me that he hit the same error when trying to compile glibc with
CFLAGS="-ggdb3", removing that part solved the problem for him. I didn't yet
retry without debugging flags (will do and report back when i've got time).

As a nice side-effect, portage is completely unusable after this error is
printed. if i re-try to emerge anything, it calculates dependencies, prints the
">>> emerge (1 of 1) sys-libs/glibc-2.3.5-r2 to /" line and then exits with 0

 # emerge info
Portage 2.0.51.22-r2 (default-linux/amd64/2005.1, gcc-3.4.3,
glibc-2.3.5-r0,glibc-2.3.5-r2, 2.6.12-gentoo-r6 x86_64)
=================================================================
System uname: 2.6.12-gentoo-r6 x86_64 AMD Opteron(tm) Processor 242
Gentoo Base System version 1.6.12
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=opteron -ggdb3 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=opteron -ggdb3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig buildpkg cache cvs debug distlocks keeptemp keepwork
multilib-strict nostrip sandbox sfperms"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
LC_ALL="en_GB.UTF-8"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org"
USE="amd64 X acpi alsa avi berkdb bitmap-fonts bzip2 crypt cups curl debug dvd
eds emboss encode expat fam flac font-server foomaticdb fortran gif gnome gpm
gstreamer gtk gtk2 imagemagick imlib ipv6 jp2 jpeg kde lzw lzw-tiff motif
mozilla mp3 mpeg ncurses network nls nptl nptlonly ogg oggvorbis opengl pam
pdflib perl png python qt quicktime readline sdl spell ssl svg tcltk tcpd tiff
truetype truetype-fonts type1-fonts udev usb userlocales utf8 vorbis xml xml2
xpm xrandr xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY

[Comment 1 Simon Stelling (RETIRED) 2005-11-13 12:00:25 UTC]

Created attachment 72841 [details]
output of emerge -d glibc

[Comment 2 SpanKY 2005-11-13 13:24:07 UTC]

i'd mark this as WONTFIX myself ... -ggdb3 is known to produce bad code when
used on large packages (like glibc)

-ggdb should be fine for most things imo

[Comment 3 Simon Stelling (RETIRED) 2005-11-19 04:31:12 UTC]

indeed, stupid user ;) however, perhaps it would have been wise to add a
replace-flags -ggdb3 -ggdb. on the other hand, it's not our job to protect me
from setting stupid cflags