[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FW: Re: help: shlibs problem

On Fri, 22 Dec 2000, Sean 'Shaleh' Perry wrote:

> Is this guy right?
> -----FW: <Pine.LNX.4.10.10012221256330.6381-100000@tennyson.netexpress.ne-----
> Date: Fri, 22 Dec 2000 13:11:18 -0600 (CST)
> From: Steve Langasek <vorlon@netexpress.net>
> To: Mariusz Przygodzki <dune@home.pl>
> Subject: Re: help: shlibs problem
> Cc: debian-mentors@lists.debian.org
> On Fri, 22 Dec 2000, Mariusz Przygodzki wrote:
> > The binary package 'qub' includes the application 'qub' and the shared 
> > library 'libfunUtil'.
> > I have debian/shlibs.local with 'libfunUtil 0' but dpkg-shlibdeps says:
> > 'warning: could not find path for libfunUtil.so.0'. I have also tried with 
> > 'libfunUtil 0 qub' in shlibs.local with the same warning.
> > The binary package includes libfunUtil.so.0.0.0 and a proper symlink 
> > libfunUtil.so.0 to libfunUtil.so.0.0.0.
> > What I am doing wrong?
> Hi Mariusz,
> I recently ran into this problem myself.  Looking at the source to
> dpkg-shlibdeps, this appears to be a bug: what happens is that dpkg-shlibdeps
> uses ldd to find all the libraries that your binary 'qub' is linked against.
> Since it depends on libfunUtil, this library will show up in the list, and
> when ldd searches the *system* path, it of course won't be able to find
> libfunUtil, because it's in the package your currently building that hasn't
> been installed yet.  dpkg-shlibdeps should look at shlibs.local for libraries
> that it can't find on the system, but it does not do this.

Use dpkg-dev 1.7.2(1.7.0 and 1.7.1 had minor problems).  They no longer use
ldd, but instead use objdump.

Version: 3.12
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
Adam Heath <doogie@debian.org>        Finger Print | KeyID
67 01 42 93 CA 37 FB 1E    63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA  3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----

Reply to: