From owner-freebsd-current@FreeBSD.ORG Sun Aug 31 10:47:59 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D10516A4BF; Sun, 31 Aug 2003 10:47:59 -0700 (PDT) Received: from accms33.physik.rwth-aachen.de (accms33.physik.RWTH-Aachen.DE [137.226.46.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7326E43FCB; Sun, 31 Aug 2003 10:47:57 -0700 (PDT) (envelope-from kuku@accms33.physik.rwth-aachen.de) Received: (from kuku@localhost) by accms33.physik.rwth-aachen.de (8.11.6/8.9.3) id h7VHlff25512; Sun, 31 Aug 2003 19:47:41 +0200 Date: Sun, 31 Aug 2003 19:47:40 +0200 From: "Christoph P. Kukulies" To: Alexander Leidinger Message-ID: <20030831174739.GA25495@gilberto.physik.rwth-aachen.de> References: <200308291454.h7TEsb913915@accms33.physik.rwth-aachen.de> <20030829172348.1aa0b5d4.Alexander@Leidinger.net> <20030829161907.GA89129@troutmask.apl.washington.edu> <20030830135427.0cea7fdb.Alexander@Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030830135427.0cea7fdb.Alexander@Leidinger.net> User-Agent: Mutt/1.4i cc: gordon@freebsd.org cc: Christoph Kukulies cc: freebsd-current@freebsd.org cc: Steve Kargl Subject: Re: /lib symlinks problem? (was: Re: __fpclassifyd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2003 17:47:59 -0000 I found the problem with my system here: I had a libc.so.5 in /usr/lib of Jan 16. Concurrently the newly installed libc.so.5 lives in /lib. After removing /usr/lib/libc.so.5 the binary (httpd) worked. On Sat, Aug 30, 2003 at 01:54:27PM +0200, Alexander Leidinger wrote: > On Fri, 29 Aug 2003 09:19:07 -0700 > Steve Kargl wrote: > > > Are you linking in libc? > > > > troutmask:kargl[207] nm -D /usr/lib/libc.so | grep fpcl > > 000b0040 T __fpclassifyd > > 000afff0 T __fpclassifyf > > 000b00a0 T __fpclassifyl > > I think the problem is, that some tools have a problem finding it...: > ---snip--- > (3) netchild@ttyp1 % nm -D /usr/lib/libc.so | grep fpcl > nm: /usr/lib/libc.so: No such file or directory > > (4) netchild@ttyp1 % ll /usr/lib/libc.so > lrwxr-xr-x 1 root wheel 19B 29 Aug 13:57 /usr/lib/libc.so@ -> ../../lib/libc.so.5 > > (5) netchild@ttyp1 % ll /usr > lrwxr-xr-x 1 root wheel 7.0B 18 Aug 2001 /usr@ -> big/usr > > (7) netchild@ttyp1 % ll /lib/libc.so > lrwxr-xr-x 1 root wheel 9.0B 29 Aug 13:57 /lib/libc.so@ -> libc.so.5 > ---snip--- > > I think a workaround would be to use absolute symlinks (at least as an > option). > > > David O'Brien wrote: > > > Yes, your libs + binaries are out of sync with each other. > > You may also have stale ".so" symlinks in /usr/lib. One gets this if one > > runs a certain 4.x binary on 5.1. > > This was an update of an -current since ever system from Aug 2 src to > Aug 28 src. I just tried to recompile cdrdao. > > Bye, > Alexander. >