Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 66569 - emerge --update world screwed up important gcc libraries
Summary: emerge --update world screwed up important gcc libraries
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 All
: High critical (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-06 14:52 UTC by ivo welch
Modified: 2004-12-05 12:40 UTC (History)
0 users

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 ivo welch 2004-10-06 14:52:52 UTC
I did my first "emerge --update world" today in a couple of days.  my system is reported to be fully up-to-date right now.

alas, after the update, mozilla no longer started.  it complains
/usr/lib/mozilla/mozilla-xremote-client: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

so, I dropped out of X, and restarted kde.  turns out kde did not start, either, again complaining that libstdc++.so.6 was not found.  so I did an
 $ ls -l `locate libstdc++.so.6`
to see what the update changed.  apparently, some package moved me to /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.4.2 , whereas it was earlier /3.4.1 .  I can restart kde by sym-linking 3.4.1 to 3.4.2.  kde now finds libstdc++.so.6 and is happy.  (mozilla still does not find it.)

I wish I could tell you what packages "emerge world" updated for me today to tell you what package is at fault, but I do not know where the emerge log is kept.  sorry.  I also do not know how to query emerge as to where libstdc++.so.6 lives in.  again, mea culpa.  hope this part is obvious to you wizards.

regards, /iaw


# emerge info
Portage 2.0.50-r11 (gcc34-2004.2, gcc-3.4.1, glibc-2.3.4.20040808-r0, 2.6.7-gentoo-r14)
=================================================================
System uname: 2.6.7-gentoo-r14 x86_64 4
Gentoo Base System version 1.4.16
distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-pipe -O2"
CHOST="x86_64-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.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/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-pipe -O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache"
GENTOO_MIRRORS=" http://mirror.clarkson.edu/pub/distributions/gentoo/ ftp://gentoo.mirrors.pair.com/ http://ftp.heanet.ie/pub/gentoo/ ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mirrors.sec.informatik.tu-darmstadt.de/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 aalib alsa amd64 apm arts avi berkdb bitmap-fonts bonobo cdr crypt cups directfb encode esd f77 fam flac foomaticdb g77 gdbm ggi gif gnome gphoto2 gpm gtk gtk2 gtkhtml guile imagemagick imlib java jpeg kde ldap libg++ libwww mad mikmod motif mozilla mpeg mysql nas ncurses nls oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline ruby scanner sdl slang snmp spell ssl tcltk tcpd tetex tiff truetype ungif usb xml xml2 xmms xprint xv zlib"
Comment 1 Stefan Tittel 2004-10-07 12:19:45 UTC
I can confirm this bug updating from gcc-3.4.1-r2 to gcc-3.4.2-r2 on amd64 (on which both packages are supposed to be STABLE!). 


As Travis wrote in a comment to bug 65219 the following fixes it (make sure you use gcc-config-1.3.6-r2 or later):

gcc-config <arch>-3.4.2
fix_libtool_files.sh <previous compiler version>

where <arch> is probably i686-pc-linux-gnu on x86 and x86_64-pc-linux-gnu on amd64.... and <previous compiler version> is probably 3.4.1 or 3.3.3.


Since gcc-config does it's job correctly when called manually, I don't think this is a duplicate of bug 65129. Obviously gcc-config and/or fix_libtool_files.sh are not called appropriately in the gcc-3.4.2-r2 ebuild.

BTW: Shouldn't the ebuild depend on >=sys-devel/gcc-config-1.3.6-r2 instead of >=sys-devel/gcc-config-1.3.1?
Comment 2 Stefan Tittel 2004-10-07 12:21:30 UTC
Sorry, I meant bug 65129 not 65219 .
Comment 3 SpanKY gentoo-dev 2004-12-05 12:40:08 UTC
should be resolved now