Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Dec 2012 23:17:20 +0000 (UTC)
From:      Walter Hurry <walterhurry@gmail.com>
To:        freebsd-stable@freebsd.org
Subject:   Re: Will we get a RELEASE-9.1 for Christmas?
Message-ID:  <kab3a0$3jk$1@ger.gmane.org>
References:  <201212090318.UAA11257@lariat.net> <50C412F6.7040300@sdf.org> <201212090526.26535.lumiwa@gmail.com> <CAJHU=or2MJ7cNz2p4v%2BYFcOjgV-2dXrxngTeUCkxU8kOqOoFaQ@mail.gmail.com> <CAN6yY1vQPf8NUiq9fqr-qPDYSjON%2BMhXuQd6bHbQWtCbJ%2Byyqw@mail.gmail.com> <50C8CF77.2040102@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Dec 2012 18:39:51 +0000, Matthew Seaman wrote:

> On 12/12/2012 17:38, Kevin Oberman wrote:
>> If you use pkgng, please try editing /usr/local/sbin/pkg_libchk to
>> replace "pkg_info" with "pkg info" in all locations and let me know how
>> it works, . I'm hoping that will make it work with pkgng, but I have no
>> way to check as I can't currently use pkgng on any of my systems, yet.
> 
> I'd like to draw people's attention to one of the newer capabilities of
> pkgng as it's directly relevant to this problem.  You can use pkgng to
> track which shared libraries are used by binaries in all packages.
> Shared library use is determined by analysing the dynamic loading
> information recorded in ELF binaries -- either executables or shared
> libraries -- so it's pretty reliable.
> 
> The feature is turned off by default, but you can enable it by adding:
> 
> SHLIBS: YES
> 
> to ${LOCALBASE}/etc/pkg.conf and then generate the shlib info by:
> 
> pkg check -Ba
> 
> This will take a while on a system with lots of packages installed: it
> will investigate every file installed by every package.  If you aren't
> using a repo where the shlibs function is enabled, you'll have to use
> pkg check thike this on any new pkgs you subsequently install.
> 
> Then, for example, you can find all the pkgs with files that link
> against, say, libssh2 by:
> 
> worm:~:% pkg query -a "%n-%v %B" | grep libssh2 curl-7.24.0_1
> libssh2.so.1

That looks like a useful feature. But why is it saying this?

pkg: (firefox-17.0.1,1) shared library libxpcom.so not found
pkg: (firefox-17.0.1,1) shared library libmozalloc.so not found
(lots more output snipped)

$ locate libxpcom.so
/usr/local/lib/firefox/libxpcom.so
$ locate libmozalloc.so
/usr/local/lib/firefox/libmozalloc.so
$ file /usr/local/lib/firefox/libxpcom.so
/usr/local/lib/firefox/libxpcom.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (FreeBSD), dynamically linked, stripped
$ file /usr/local/lib/firefox/libmozalloc.so
/usr/local/lib/firefox/libmozalloc.so: ELF 64-bit LSB shared object, 
x86-64, version 1 (FreeBSD), dynamically linked, stripped
$ 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?kab3a0$3jk$1>