From owner-freebsd-questions Mon May 10 4:27:19 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 65C12153E1 for ; Mon, 10 May 1999 04:27:11 -0700 (PDT) (envelope-from tom@embt.com) Received: from gizmo (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id GAA11259 for ; Mon, 10 May 1999 06:21:44 -0500 (CDT) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19990510073014.009028d4@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 10 May 1999 07:30:14 -0400 To: freebsd-questions@freebsd.org From: Tom Embt Subject: linux_libs & ldconfig (Bad address) not working ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't recall exactly what I did to break it, but I am having trouble with my linux_libs. Running the linux ldconfig gives the following: odin# /compat/linux/sbin/ldconfig /compat/linux/sbin/ldconfig: warning: can't open /usr/lib (Bad address), skipping /compat/linux/sbin/ldconfig: warning: can't open /lib (Bad address), skipping If I completely remove and reinstall the linux_lib-2.6.1 port, I get essentially the same error message during the installation phase. Running a Linux binary of quake2 (which used to work perfectly) results in: odin# ./quake2 +set dedicated 1 ./quake2: can't open cache '/etc/ld.so.cache' ./quake2: can't load library 'libdl.so.1' Can anybody tell me what's going on? PS- I don't know if it's related but I seem to have UNREFerenced files on / , and no matter how much I run fsck, it won't get rid of them or pronounce the filesystem clean. I don't see how this could be directly related, as /compat/linux is actually a symlink to /usr/compat/linux (for space reasons). Have I F'ed up my system? Thanks, Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message