I upgraded to emul-linux-x86-glibc-2.3.4.20041102 as part of a dependency for 2.3.4.20041102-r1. Now, Doom 3, Enemy Territory, and Openoffice no longer work. Downgrading to emul-linux-x86-glibc-1.1 solved the problem. Others have complained of this problem as well here: http://forums.gentoo.org/viewtopic-t-309613.html Firefox-bin however, the only other 32-bit application I use, works just fine with this version of the glibc emulation package. Downgrading to emul-linux-x86-glibc-1.1 solves the problem completely and all 32-bit applications go back to working normally. Reproducible: Always Steps to Reproduce: 1. Upgrade to emul-linux-x86-glibc-2.3.4.20041102 2. Try to run Openoffice, Doom 3, or Enemy Territory 3. Actual Results: Doom 3 exits with: ----- R_InitOpenGL ----- Setup X display connection dlopen(libGL.so.1) Segmentation fault Enemy Territory exits with: ----- Client Initialization Complete ----- ----- R_Init ----- ...loading libGL.so.1: Segmentation fault OpenOffice exits with: Gnome session manager detected - session management disabled I18N: X Window System doesn't support locale "en_US" I18N: X Window System doesn't support locale "C" Segmentation fault Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r4 x86_64) ================================================================= System uname: 2.6.11-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 26 2005, 03:30:37)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O3 -march=k8 -pipe -fweb -ftracer -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=k8 -pipe -fweb -ftracer -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="ftp://mirrors.tds.net/gentoo ftp://ftp.ndlug.nd.edu/pub/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X acpi alsa berkdb bitmap-fonts cdr crypt cups curl dvd fam flac font-server foomaticdb fortran gif gnome gpm gstreamer gtk gtk2 hal imlib ipv6 java joystick jp2 jpeg lzw lzw-tiff mad mp3 multilib ncurses nls nptl nptlonly oggvorbis opengl pam perl png ppds python readline spell ssl tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xml2 xmms xpm xprint xrandr xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
please take a look at that. emul-linux-x86-glibc-1.1 is masked btw., what's the reason for that?
could you try to update your system to 2005.0 and see if this is still an issue? we made quite a lot of changes between these two profiles regarding 32-bit-emulation
It is no longer an issue. I upgraded to 2005.0 a while ago and it solved all of my emul lib problems.
see comment #3
ermmm.... I don't know if it fits here but I'll ran into problems with the 32bit emulation libraries for AMD64 since upgrading to 2005.0. My ET servers will crash constantly within 5 minutes up to 1 day. The error message in `dmesg` is: ------ CUT HERE ;) ------- etded.x86[4749]: segfault at 00000000ff7fdff4 rip 0000000008097495 rsp 00000000ff7fdff0 error 6 etded.x86[4749] bad frame in 32bit rt signal setup frame:00000000ff7fdc70 rip:8097495 rsp:ff7fdff0 orax:ffffffffffffffff etded.x86[5267]: segfault at 00000000ff7fdff4 rip 0000000008097495 rsp 00000000ff7fdff0 error 6 etded.x86[5267] bad frame in 32bit rt signal setup frame:00000000ff7fdc70 rip:8097495 rsp:ff7fdff0 orax:ffffffffffffffff ------ CUT HERE ;) ------- I should mention that the hardware was changed. That means new CPU, new RAM, new network card, new motherboard and so on. So it should not be an RAM issue. Does it fit or should I open another bug request or any ideas :D ?
Stephan, that's a different bug, so please open a new one :)
