From owner-freebsd-questions Tue Dec 25 4:39:19 2001 Delivered-To: freebsd-questions@freebsd.org Received: from primus.vsservices.com (primus.vsservices.com [63.66.136.75]) by hub.freebsd.org (Postfix) with ESMTP id 2738F37B417 for ; Tue, 25 Dec 2001 04:39:17 -0800 (PST) Received: from prime.vsservices.com (conr-adsl-dhcp-26-38.txucom.net [209.34.26.38]) by primus.vsservices.com (8.11.3/8.11.3) with SMTP id fBODqZB50378; Mon, 24 Dec 2001 05:52:36 -0800 (PST) (envelope-from gclarkii@vsservices.com) Content-Type: text/plain; charset="iso-8859-1" From: GB Clark II To: , Subject: Re: shared object "libc.so.6" not found Date: Mon, 24 Dec 2001 07:52:37 -0600 X-Mailer: KMail [version 1.2] References: <160c901c18c6c$06464670$2900740a@cableone.net> In-Reply-To: <160c901c18c6c$06464670$2900740a@cableone.net> MIME-Version: 1.0 Message-Id: <0112240752370P.65128@prime.vsservices.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 24 December 2001 05:13, dennyboy@cableone.net wrote: > had installed netscape, the bsd version, since > the linux version never worked due to not being > able to find the lib files it needed. Same story > with the bsd version. Tried copying libXt.so.6 > & libXtst.so.6.1 to several lib directories and > then creating the soft links, but it still would > not work. After rebooting & attempting to startx, > got the following message: > /usr/libexec/ld-elf.so.1: Shared object "libc.so.6" > not found. > Can someone tell me how to fix this? I hate to do > a complete reinstall. Everything else is working > fine. Thanks. > That almost has to be a Linux binary. Last time I checked, FreeBSD does not have a version 6 libc. GB -- GB Clark II | Roaming FreeBSD Admin gclarkii@VSServices.COM | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message