From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 18 22:12:38 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34F77106566B for ; Sat, 18 Feb 2012 22:12:38 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id E47D78FC08 for ; Sat, 18 Feb 2012 22:12:37 +0000 (UTC) Received: by iaeo4 with SMTP id o4so7872647iae.13 for ; Sat, 18 Feb 2012 14:12:37 -0800 (PST) Received-SPF: pass (google.com: domain of chmeeedalf@gmail.com designates 10.50.202.97 as permitted sender) client-ip=10.50.202.97; Authentication-Results: mr.google.com; spf=pass (google.com: domain of chmeeedalf@gmail.com designates 10.50.202.97 as permitted sender) smtp.mail=chmeeedalf@gmail.com; dkim=pass header.i=chmeeedalf@gmail.com Received: from mr.google.com ([10.50.202.97]) by 10.50.202.97 with SMTP id kh1mr4637258igc.19.1329603157523 (num_hops = 1); Sat, 18 Feb 2012 14:12:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=QF6ef4PGZzrHRmiHZuVbThumZ7SCXMGumWfug8ghPLI=; b=DFOg75syrf3lE0JCH7cw5+dsgaESH1NsYSSpBP4uC0dUCv+60BvYqdgqNe+ntmxuqd 4D2SwSxdKPMOiQnWBjeTfYG2aDGLIfZCQtv13NAdx8YDXIWhG5GFVIdOZd+r/7366yVf 9dBtoXLySorAOTq/JF8w/4gD8dR8W3qyiY6GY= Received: by 10.50.202.97 with SMTP id kh1mr3762996igc.19.1329603156642; Sat, 18 Feb 2012 14:12:36 -0800 (PST) Received: from narn.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com. [216.15.41.8]) by mx.google.com with ESMTPS id wn7sm2645363igc.0.2012.02.18.14.12.35 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 18 Feb 2012 14:12:36 -0800 (PST) Date: Sat, 18 Feb 2012 17:12:18 -0500 From: Justin Hibbits To: Rob Ballantyne Message-ID: <20120218171218.323c614b@narn.knownspace> In-Reply-To: References: X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; powerpc-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Some ports not building shared libraries X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2012 22:12:38 -0000 On Sat, 18 Feb 2012 13:58:03 -0800 Rob Ballantyne wrote: > Hi All, > > I ran into this while trying to install emacs. The chain of > dependancies leads to package fribidi-0.19.2_1. It seems emacs looks > for a shared library that is supposed to be built via this package. > > If I build: > > > mac# make install > ===> Installing for fribidi-0.19.2_1 > ===> fribidi-0.19.2_1 depends on executable: pkg-config - found > ===> Generating temporary packing list > ===> Checking if converters/fribidi already installed > gmake install-recursive > > > .... > > ===> Compressing manual pages for fribidi-0.19.2_1 > ===> Running ldconfig > /sbin/ldconfig -m /usr/local/lib > ===> Registering installation for fribidi-0.19.2_1 > > > everything works just fine but notice: > > mac# ls -l /usr/local/lib/libfri* > -rw-r--r-- 1 root wheel 122646 Feb 18 > 13:53 /usr/local/lib/libfribidi.a -rwxr-xr-x 1 root wheel 876 > Feb 18 13:53 /usr/local/lib/libfribidi.la > > And, now if I try to remove it: > > mac# pkg_delete fribidi-0.19.2_1 > pkg_delete: file '/usr/local/lib/libfribidi.so' doesn't exist > pkg_delete: file '/usr/local/lib/libfribidi.so.3' doesn't exist > pkg_delete: couldn't entirely delete package `fribidi-0.19.2_1' > (perhaps the packing list is incorrectly specified?) > mac# > > Is this a known issue? (I searched but couldn't find anything). > > Is there a trick (standard or otherwise) to get the build to build the > necessary shared library. > > (I've run into this on at least one other occasion but I can't recall > the package involved in that case). > > Thanks for any advice! > > Rob Hi Rob, I ran into something similar to this a few months ago, and blamed it on the transition to 10-CURRENT (see the various threads on current@ for more details). Updating world and ports to recent seems to have fixed it for me. - Justin