Re: binary-or-shlib-defines-rpath error message
Le Thursday 11 October 2007 15:17:06 varun_shrivastava, vous avez écrit :
> hi
Hi !
> i am a newbee in packaging and trying out how to package some already
> available source packages
>
> i am trying to pack jpeg62_6b, the package builds successfully but running
> lintian shows
> "binary-or-shlib-defines-rpath ./usr/bin/cjpeg /usr/lib"
> the message is same for all binaries in /usr/bin
>
> can some one please explain the reason for this message?
rpath specifies where to find the required library.
Debian wants *not* to use it since it messes with library update: one may want
to move the library to a new place without breaking binaries depending on it.
> Also while building the same package a warning message is being displayed
> by dh_shlibdeps
> here is the message::
> dpkg-shlibdeps -Tdebian/libjpeg62-utils.substvars
> debian/libjpeg62-utils/usr/bin/cjpeg debian/libjpeg62-utils/usr/bin/djpeg
> debian/libjpeg62-utils/usr/bin/rdjpgcom
> debian/libjpeg62-utils/usr/bin/wrjpgcom
> debian/libjpeg62-utils/usr/bin/jpegtran
> dpkg-shlibdeps: warning: could not find path for libjpeg.so.62
> dpkg-shlibdeps: warning: could not find path for libjpeg.so.62
> dpkg-shlibdeps: warning: could not find path for libjpeg.so.62
> dpkg-shlibdeps: warning: could not find any packages for (libjpeg.so.62)
> dpkg-shlibdeps: warning: unable to find dependency information for shared
> library libjpeg (soname 62, path , dependency field Depends)
> dpkg-shlibdeps: warning: could not find any packages for (libjpeg.so.62)
> dpkg-shlibdeps: warning: unable to find dependency information for shared
> library libjpeg (soname 62, path , dependency field Depends)
> dpkg-shlibdeps: warning: could not find any packages for (libjpeg.so.62)
> dpkg-shlibdeps: warning: unable to find dependency information for shared
> library libjpeg (soname 62, path , dependency field Depends)
>
> what i figured out that the binaries that are getting installed are linking
> to the library the package will produce. Any means to provide such kind of
> information?
shlibdeps looks for libraries that the binary requires and add the
coresponding package to the dependencies of the binary package.
This loooks like you have several version of this library installed, like one
in /usr/local/lib, compiled by yourself, and it screw up shlibdeps since it
cannot find a package for it.
Romain
Reply to: