how to check dependencies of packages

Bill Maltby LFS Related lfsbill at wlmcs.com
Sat Sep 7 09:31:57 PDT 2002


On Sat, 7 Sep 2002, Archaic wrote:

> On Sat, Sep 07, 2002 at 03:27:41AM -0500, Dagmar d'Surreal wrote:
> > On Thu, 2002-09-05 at 05:46, Matthias Benkmann wrote:
> > > On Thu, 5 Sep 2002 11:58:54 +0200 "Dieter Scholz" <dscholz at reido.de>
> > > wrote:
> > > 
> > > > Is there a reliable way to find out (automatically) what build time/run
> > > > time dependencies (programs/libraries/packages/config files) a package
> > > > has? 
> > > 
> > > strace
> > 
> > I'm rather fond of just running ldd on anything that looks like a binary
> > (or shared library) since the output is IMHO much more readable. 
> 
> That won't work for compile time dependencies, though, which is what is
> being discussed in this thread. For instance, if package foo's
> {makefile,config,misc_script} calls gawk, gawk is a compile-time
> dependency. That's what strace would be used for.

Well, not a direct solution, but I believe that with only a little prep
work, cscope with some front end ldd's may do the trick. maybe don't need
the front end. It's been a long time since I used cscope.

http://cscope.sourceforge.net/cscope_man_page_html

> Archaic

Bill Maltby
billm at wlmcs.com

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message



More information about the lfs-dev mailing list