Bug 67373

Summary:	After emerging glibc-2.3.4.20040808-r1, using ldconfig gives error and appears to kill networking
Product:	Gentoo Linux	Reporter:	Alex Weiss <gg.alex.weiss>
Component:	[OLD] Library	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED INVALID
Severity:	normal	CC:	glen, lisa
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Alex Weiss 2004-10-13 05:29:52 UTC

I emerged the latest and stable version of glibc (2.3.4.20040808-r1). However, after doing so, I was unable to access the internet. If I rebooted the system I got some crash message from kde and then it rebooted. Networking started working again after that.

I tried typing in ldconfig and got an error saying that /lib/ld-linux.so.1 was not a symlink. Indeed, when I go into the lib directory that file is not a symlink and there's another file ld-linux.so.1.9.11 of the same length. Using diff to compare files indicated they were identical. 

I went back to the previous stable version of glibc (2.3.3.20040420-r2), but this did not resolve the problem.

Reproducible: Always
Steps to Reproduce:
1.Typing in ldconfig
2.
3.

Actual Results:  
I get an error informing me that ld-linux.so.1 was not a symlink and networking
appeared to die on me.

Expected Results:  
Updated all the links I imagine and have networking working.

^[]1;^G^[]2;Started emerge on: Oct 13, 2004 08:28:02^G^[]1;^G^[]2; *** emerge  $
^[]1;^G^[]2; *** terminating.^G^[]1;^G^[]2;xterm^GPortage 2.0.50-r11 (default-x$
=================================================================
System uname: 2.6.7 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer -ftracer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.$
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium3 -O2 -pipe -fomit-frame-pointer -ftracer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://ibiblio.org/pub/Linux/distributions/gentoo/ http://www.gt$
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 apm avi berkdb bitmap-fonts bonobo cdparanoia cdr crypt cups $

Comment 1 Karl Ernst Brunk 2004-10-21 13:32:08 UTC

same on my system.
I deleted ld-linux.so.1 and made a symbolic link of ld-linux.so.1.9.11.
I am wondering, what ldconfig is doing when it is called after an emerge. There are no error messages!

Comment 2 Elan Ruusamäe 2004-10-21 14:07:49 UTC

/lib/ld-linux.so.1?

strange, i checked all systems i have access, and they have
/lib/ld-linux.so.2

even the oldest system i got, has this:
/lib/ld-linux.so.2 -> ld-2.2.5.so

is this on x86?

Comment 3 Alex Weiss 2004-10-21 20:11:42 UTC

Hi,

The problem is solved. I merely deleted the bad file which was not a link, but the actual file and re-ran ldconfig.

Best,

Alex

Comment 4 Travis Tilley (RETIRED) gentoo-dev

2004-10-23 11:50:28 UTC

closing