Re: porting: reverse engireering a packages dependencies

On Wednesday, July 16, 2003, at 07:39  PM, David R. Morrison wrote:

> 3) When everything is compiled, look for all the executables and 
> libraries
> your package has created, and run "otool -L" on them.  This tells you
> which libraries they link to, and in the case of /sw/lib/..., the 
> library
> will be provided by a fink package.

One aspect of this that may not be obvious when moving to fink: since 
binary packages are stored as .debs, you can find the name of the fink 
package with dpkg:

$ otool -L /sw/lib/ivl/ivl
/sw/lib/ivl/ivl:
        /sw/lib/libdl.0.dylib (compatibility version 0.0.0, current 
version 0.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
current version 63.0.0)

$ dpkg --search /sw/lib/libdl.0.dylib
dlcompat-shlibs: /sw/lib/libdl.0.dylib

which means that you need to list dlcompat-shlibs in the dependencies 
section. Usually, this means that there is a corresponding -dev package 
for the build dependencies: dlcompat-dev, in this case.

--
Charles Lepple <clepple@xxxxxx>
http://www.ghz.cc/charles/



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0