Re: Making Debian Packages from tar ball files

[Bill Moseley <moseley@hank.org>]

On Fri, May 16, 2003 at 12:25:03PM -0400, David Z Maze wrote:
> (debian-mentors might be a better mailing list for this.)

Ah, thanks.  I'll post there too.

> > dpkg-shlibdeps: warning: could not find any packages for 
> > /usr/local/lib/libswish-e.so.2 (libswish-e.so.2)
> 
> If you have dependencies on things installed locally, that'll cause
> problems for the generated package.  I'd remove the library in
> /usr/local/lib; if your package really does depend on it, you might
> need to package other libraries.  (I'm not clear if the Debian swish-e
> package provides the library you need or not.)

I'm not clear what you are saying.  The swish-e distribution builds libswish-e as well as 
the swish-e binary.  The swish-e binary is linked against libswish-e (where libswish-e is a 
shared lib on most platforms).  There's no dependencies on anything install locally.

If I build the source package like this using a prefix:

   moseley@bumby:~/f$ ../swish-e/configure --prefix=$HOME/f2 >/dev/null \
                && make >/dev/null 
                && make install >/dev/null

note that the run-time linkages are correct (they point to the libswish-e I just built):


   moseley@bumby:~/f$ ldd ~/f2/bin/swish-e 
        libxml2.so.2 => /usr/lib/libxml2.so.2 (0x4001b000)
        libswish-e.so.2 => /home/moseley/f2/lib/libswish-e.so.2 (0x400fc000)
        libz.so.1 => /lib/libz.so.1 (0x40118000)
        libm.so.6 => /lib/libm.so.6 (0x40125000)
        libc.so.6 => /lib/libc.so.6 (0x40146000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

so what's odd is why debian/rules ended up creating a binary with run-time linkages pointing 
to the lib in /usr/local.

I'm using a default rules files created by dh_make that does:

  /configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr \
        --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info


-- 
Bill Moseley
moseley@hank.org