Re: Bug#307502: illuminator: ftbfs [sparc] could not find path for libluminate.so.6

[Hendrik Sattler <ubq7@stud.uni-karlsruhe.de>]

Am Dienstag, 3. Mai 2005 18:46 schrieb Adam C Powell IV:
> On Tue, 2005-05-03 at 08:59 -0700, Blars Blarson wrote:
> > Package: illuminator
> > dh_makeshlibs -a
[...]
> > dh_shlibdeps -a
> > dpkg-shlibdeps: warning: could not find path for libluminate.so.6

> Actually, since it built successfully on ten other arches, I'd conclude
> this is a buggy sparc toolchain.  What other explanation can you offer?

Or you had luck on ten of them and one chokes about a missing option to 
dh_shlibdeps?
Since you have a split package, I cite the manpage dh_shlibdeps(1):
----------------------------snip------------------------------------
EXAMPLES
     Suppose that your source package produces libfoo1, libfoo-dev, and lib-
     foo-bin binary packages. libfoo-bin links against libfoo1, and should
     depend on it. In your rules file, first run dh_makeshlibs, then
     dh_shlibdeps:
             dh_makeshlibs
             dh_shlibdeps -L libfoo1 -l debian/libfoo1/usr/lib
     This will have the effect of generating automatically a shlibs file for
     libfoo1, and using that file and the libfoo1 library in the debian/lib-
     foo1/usr/lib directory to calculate shared library dependency informa-
     tion.
----------------------------snip------------------------------------

So I suggest changing the dh_shlibdeps line from
 dh_shlibdeps -a
to
 dh_shlibdeps -L libilluminate6 -l debian/libilluminate6/usr/lib

AFAIK, it is pure luck if ldd works without those.

HS