Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Feb 2012 17:12:18 -0500
From:      Justin Hibbits <chmeeedalf@gmail.com>
To:        Rob Ballantyne <robballantyne3@gmail.com>
Cc:        freebsd-ppc@freebsd.org
Subject:   Re: Some ports not building shared libraries
Message-ID:  <20120218171218.323c614b@narn.knownspace>
In-Reply-To: <CAKLrb5cXAcTh=TDXK6efFJDAZVNgmOpyNbMMGvb7MuLq5CAgrw@mail.gmail.com>
References:  <CAKLrb5cXAcTh=TDXK6efFJDAZVNgmOpyNbMMGvb7MuLq5CAgrw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 18 Feb 2012 13:58:03 -0800
Rob Ballantyne <robballantyne3@gmail.com> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120218171218.323c614b>