Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 55826 - Serious trouble with old (gcc 3.3.x linked) binaries though libstdc++
Summary: Serious trouble with old (gcc 3.3.x linked) binaries though libstdc++
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-01 13:45 UTC by Florian Huber
Modified: 2004-07-27 22:41 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Huber 2004-07-01 13:45:12 UTC
Since switching to the gcc 3.4 amd64 profile I could not run several programs (pekwm, groff, firefox) anymore. They all terminated with an error message like:

$BINARY:   relocation error: /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.3/32/libstdc++.so.5: symbol _Unwind_SjLj_Register, version GCC_3.0 not defined in file libgcc_s.so.1 with link time reference

This could be fixed with a simple recompile, but binary packages do still not work.

Reproducible: Always
Steps to Reproduce:
1. Switched to amd64 gcc 3.4 profile
2. emerge -u world
3. start one of the above programs




 $ emerge info
Portage 2.0.50-r8 (gcc34-amd64-2004.1, gcc-3.4.0, glibc-2.3.4.20040605-r0, 2.6.7
)
=================================================================
System uname: 2.6.7 x86_64 4
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2"
CHOST="x86_64-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/s
hare/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache fixpackages sandbox"
GENTOO_MIRRORS="ftp://172.16.0.1/ http://ftp.tu-clausthal.de/pub/linux/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage"
USE="X X509 acpi alsa amd amd64 avi berkdb cddb crypt curl devfs26 dga diet divx
4linux dv dvb dvd dvdr encode esd ethereal ffmpeg flash fmod freetype gd gdbm gi
f gimp gtk gtk2 icq imagemagick imap imlib imlib2 ipv6 jabber jikes jpeg libwww 
maildir memlimit mpeg mpeg4 multilib ncurses nls nptl nvidia offensive oggvorbis
 opengl openssh pam pcap pdflib perl pic plotutils png python qhull quicktime re
adline scanner sdk sdl slang speedo src ssl tcc tiff transcode truetype type1 un
icode usb v4l v4l2 vim-with-x wmf xface xine xml xml2 xmms xosd xv xvid zlib zvb
i"

Maybe it has also to do with nptl?
Comment 1 Florian Huber 2004-07-05 04:36:45 UTC
SOLUTION (works for me at least): I just unmerged the gcc 3.3.x (for me emerge unmerge sys-devel/gcc-3.3.3-r6) and now the libstdc++-v3 libs are used.

AFAICS everything's working now, also java.

Maybe gcc < 3.4 should be masked for the 2004.1 gcc 3.4 amd 64 profile?
Comment 2 Travis Tilley (RETIRED) gentoo-dev 2004-07-05 10:11:08 UTC
<3.4 is already masked in the gcc34-amd64-2004.1 profile, but it cant force you to uninstall 3.3.x

another solution would be to delete /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.3/libstdc++.so, which is just a symlink... but that isnt exactly an elegant solution.
Comment 3 Travis Tilley (RETIRED) gentoo-dev 2004-07-27 22:41:44 UTC
cant force people to uninstall gcc 3.3.3