From owner-freebsd-ports@FreeBSD.ORG Sat Mar 26 10:12:05 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0467106564A for ; Sat, 26 Mar 2011 10:12:05 +0000 (UTC) (envelope-from dennylin93@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3571F8FC08 for ; Sat, 26 Mar 2011 10:12:05 +0000 (UTC) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 1001) id 3EE984B7844; Sat, 26 Mar 2011 17:55:14 +0800 (CST) Date: Sat, 26 Mar 2011 17:55:14 +0800 From: Denny Lin To: "Edward Sanford Sutton, III" Message-ID: <20110326095514.GQ129@mail.hs.ntnu.edu.tw> References: <201103260229.16197.mirror176@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <201103260229.16197.mirror176@cox.net> User-Agent: Mutt/1.4.2.3i Cc: ports@freebsd.org Subject: Re: How to best handle ports mislinking against locally installed copies? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2011 10:12:05 -0000 On Sat, Mar 26, 2011 at 02:29:14AM -0700, Edward Sanford Sutton, III wrote: > As an example, net/avahi-app fails to build on my machine because of the > error: > /libexec/ld-elf.so.1: Shared object "libicui18n.so.38" not found, required > by "libavahi-glib.so.1" > This can be fixed by removing the port before building so that it is unable to > link against /usr/local/lib/libavahi-glib.so.1 and instead correctly links > against ./work/avahi-0.6.29/avahi-glib/.libs/libavahi-glib.so.1 but is it > correct to assume uninstall is needed before attempting to build a new > version or are there suggested fixes or examples of working through this? > I can try to dig up other examples I have ran into in detail but was wondering > about the general approach and if the freebsd ports tree likes to fix it, > note it, or ignore it? These are usually documented in /usr/ports/UPDATING, so check it before updating ports. Usually a rebuild fixes the problem, but sometimes a lot of ports have to be reinstalled, so it is time consuming. Try out ports-mgmt/portmaster and use the -w flag to preserve libs. They will end up in /usr/local/lib/compat/pkg/lib/ until you decide to remove them. -- Denny Lin