From owner-freebsd-questions@FreeBSD.ORG Thu Jan 15 05:02:25 2009 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 108F11065672 for ; Thu, 15 Jan 2009 05:02:25 +0000 (UTC) (envelope-from remegius@comcast.net) Received: from QMTA07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id E4F5B8FC17 for ; Thu, 15 Jan 2009 05:02:24 +0000 (UTC) (envelope-from remegius@comcast.net) Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA07.emeryville.ca.mail.comcast.net with comcast id 3ctJ1b00D0FhH24A7h2Rxp; Thu, 15 Jan 2009 05:02:25 +0000 Received: from bsd.remdog.net ([76.102.24.75]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id 3h2R1b0031dCpWs8Uh2Ri3; Thu, 15 Jan 2009 05:02:25 +0000 Message-ID: <496EC360.1050804@comcast.net> Date: Wed, 14 Jan 2009 21:02:24 -0800 From: Rem P Roberti User-Agent: Thunderbird 2.0.0.18 (X11/20081220) MIME-Version: 1.0 To: FreeBSD References: <496EAFE4.9040909@comcast.net> <62021932-6698-4362-8A94-4CF50AC5DFED@goldmark.org> <496EBFBB.5090409@comcast.net> In-Reply-To: <496EBFBB.5090409@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Launching Vim 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: Thu, 15 Jan 2009 05:02:25 -0000 > >> On Jan 14, 2009, at 9:39 PM, Rem P Roberti wrote: >> >>> Can someone give me a heads up on this. I just installed vim, but >>> when I try to launch >>> the program I get this error message: >>> >>> /libexec/ld-elf.so.1: Shared object "libperl.so" not found, required >>> by "vim" >>> >>> Is this a path problem? The actual file libperl.so recides in >>> /usr/local/lib/perl5/5.8.9/mach/CORE/libperl.so >> >> I take it that you also recently upgraded perl. Did you follow the >> instructions in /usr/ports/UPDATING regarding perl? >> >> I'm not sure that this will solve your problem, but it might. >> >> Cheers, >> >> -j >> >> > Oops...haven't checked UPDATING. I'll get on that now. Thanks. > > Rem > > Well...I checked UPDATING and ran the perl script referenced, and vim isn't one of the affected programs. So still have the problem. Rem