From owner-freebsd-stable@FreeBSD.ORG Tue May 11 17:18:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88E461065674 for ; Tue, 11 May 2010 17:18:54 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 14CD38FC1C for ; Tue, 11 May 2010 17:18:53 +0000 (UTC) Received: (qmail 17129 invoked by uid 399); 11 May 2010 17:18:52 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 11 May 2010 17:18:52 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4BE9917B.3090104@FreeBSD.org> Date: Tue, 11 May 2010 10:18:51 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Jeremy Chadwick References: <20100511041119.GA78693@icarus.home.lan> In-Reply-To: <20100511041119.GA78693@icarus.home.lan> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, lhmwzy Subject: Re: How to clear the 32-bit ldconfig error in 64-bit FreeBSD? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2010 17:18:54 -0000 On 05/10/10 21:11, Jeremy Chadwick wrote: > On Tue, May 11, 2010 at 11:11:34AM +0800, lhmwzy wrote: >> like this: >> >> ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib >> /usr/local/lib/compat >> 32-bit compatibility ldconfig path: /usr/local/lib32/compat >> .: Can't open %%RC_SUBR%%: No such file or directory This looks like an artifact from before the change removing the %%RC_SUBR%% macro. If you still have that in the rc.d file then reinstalling the port should fix it up. If it does not, please report that issue on freebsd-ports@. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/