Re: dpkg-shlibdeps: couldn't find library [...]
- To: David Paleino <d.paleino@gmail.com>
- Cc: Debian-Med <debian-med@lists.debian.org>
- Subject: Re: dpkg-shlibdeps: couldn't find library [...]
- From: Andreas Tille <tillea@rki.de>
- Date: Fri, 2 Nov 2007 22:11:35 +0100 (CET)
- Message-id: <Pine.LNX.4.64.0711022203200.16959@wr-linux02>
- In-reply-to: <20071102193042.033bcb17@matrix>
- References: <20071102193042.033bcb17@matrix>
On Fri, 2 Nov 2007, David Paleino wrote:
$ debuild
...
dh_makeshlibs
dh_shlibdeps
dpkg-shlibdeps: failure: couldn't find library libvtkCommonTCL.so (note: only
packages with 'shlibs' files are looked into). dh_shlibdeps: command returned
Remark: This is a wild guess without testing (I havn't set up a pbuilder
environment at home yet, because I have only 384MBit DSL).
I would try to use pbuilder to verify that all Build-Depends are mentioned
that are really needed. The cause of this problem _might_ _be_ that you
by chance has a package installed on your building machine which enables
the building up to this point but fails when seeking libvtkCommonTCL.so
which is in package
$ apt-file search libvtkCommonTCL
vtk-tcl: usr/lib/libvtkCommonTCL.so
....
which is not in your build-depends (neither directly nor indirectly).
libvtkCommonTCL.so is contained into vtk-tcl: I've added it to bioimagesuite
Depends, also to libbioimagesuite2, but nothing changes. Supposing that was a
RPATH-related issue [1], I've "chrpath -d"'ed all *.so files, but this didn't
help either.
Mentioning the package in the Depends is not sufficient - it has to be in
Build-Depends. I do not think that [1] is related because you are not
dealing with a private library but with a library in some other package.
(we would have a new package which might be very useful to our users).
I'd really appreciate this.
Hope this helps and thanks for your work on this package
Andreas.
[1] http://lists.debian.org/debian-devel/2007/09/msg00889.html
--
http://fam-tille.de
Reply to: