From owner-freebsd-questions@FreeBSD.ORG Wed Jan 9 00:33:07 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 545CB16A46C for ; Wed, 9 Jan 2008 00:33:07 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AE73D13C45A; Wed, 9 Jan 2008 00:33:06 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47841641.5070204@FreeBSD.org> Date: Wed, 09 Jan 2008 01:33:05 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Schiz0 References: <8d23ec860801081625l597ab5fcx18970bde74a13692@mail.gmail.com> In-Reply-To: <8d23ec860801081625l597ab5fcx18970bde74a13692@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: User Questions Subject: Re: Upgrade to 7.0; Shared Object Not Found X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2008 00:33:07 -0000 Schiz0 wrote: > Hey, > > I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE > > # uname -a > FreeBSD Mercury 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Tue Jan 8 > 15:07:49 EST 2008 > root@Mercury:/usr/obj/usr/src/sys/SCHIZ0NET_MERCURY i38 > > > Now, whenever I run any various commands, I get various errors: > > # vim > /libexec/ld-elf.so.1: Shared object "libncurses.so.6" not found, > required by "vim" > # portupgrade > /libexec/ld-elf.so.1: Shared object "libcrypt.so.3" not found, > required by "ruby18" > # bash > /libexec/ld-elf.so.1: Shared object "libncurses.so.6" not found, > required by "bash" > And so on... > > It had me locked out at first because my default shell is bash. But I > got it working with /bin/csh now. > > So. Apparently I'm missing some shared objects. Can anyone shed any > light on the issue? Or guide me on how to fix it? Part of the upgrade that you omitted was to install new 7.0 versions of your installed ports. portupgrade -fa or -faP. Kris