Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Mar 2006 15:51:50 -0600
From:      Eric Schuele <e.schuele@computer.org>
To:        Steven Lake <steven.lake@corecomm.com>
Cc:        questions@freebsd.org
Subject:   Re: dependencies
Message-ID:  <44270CF6.1010009@computer.org>
In-Reply-To: <5.2.0.9.2.20060326163850.01ab2eb8@pop.voyager.net>
References:  <5.2.0.9.2.20060326150042.01b9d040@pop.voyager.net>	<5.2.0.9.2.20060326131808.00bf56a8@pop.voyager.net>	<5.2.0.9.2.20060326131808.00bf56a8@pop.voyager.net>	<5.2.0.9.2.20060326150042.01b9d040@pop.voyager.net> <5.2.0.9.2.20060326163850.01ab2eb8@pop.voyager.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Steven Lake wrote:
>         I'm thinking it was ld or something that I used.  

yep... ldd.

> It gave the 
> dependency for a given program, then listed either the path to the file 
> or said it was "not found".  That's mostly what I'm looking at.  I'm 
> trying to figure out which dependencies are missing for a given program 
> so I can figure out what I need to do to fix it.
> 
> At 04:39 PM 3/26/2006 -0500, Chris Hill wrote:
>> On Sun, 26 Mar 2006, Steven Lake wrote:
>>
>>>        Hmm, definitely useful, but not quite what I'm looking for.
>>
>> What precisely *are* you looking for? A little detail would go a long 
>> way here. That is: what is it that won't run? Why do you think it's a 
>> dependency issue? What have you already tried?
>>
>> Rereading your original post, it looks like you want to know not only 
>> what the dependencies are, but also which ones are not installed. 
>> Correct? Assuming yes, then you could do something like this (using my 
>> previous firefox example):
>> $ pkg_info -Rr firefox-1.5.0.1_1,1
>> Information for firefox-1.5.0.1_1,1:
>>
>> Depends on:
>> Dependency: pkgconfig-0.20
>> Dependency: expat-2.0.0_1
>> [blah blah]
>>
>> ...then do a pkg_info on each item listed, e.g.
>> $ pkg_info pkgconfig-0.20
>> ...and so on for each listed dependency. For each one, you will either 
>> get a rash of information (meaning the package is installed) or 
>> "pkg_info: can't find package 'foobar' installed or in a file!" 
>> (meaning the package is not installed). There is probably a more 
>> automated, less tedious way to do this, but I'm drawing a blank right 
>> now.
>>
>> Then again, it may be an entirely different issue - it could be a 
>> matter of packages being confused about what their dependencies really 
>> are. You may see this when trying to update. This can be fixed using 
>> cvsup, pkgdb, portsdb and friends. See the many recent threads about 
>> updating ports and/or packages.
>>
>>> At 01:40 PM 3/26/2006 -0500, Chris Hill wrote:
>>>> On Sun, 26 Mar 2006, Steven Lake wrote:
>>>>
>>>>>         Hi all.  Ok, I'm having a total brain fart today.  I've got 
>>>>> a few apps that won't run and I need to find out the list of 
>>>>> dependencies and what they're missing.  But I can't remember for 
>>>>> the life of me what the command I need is to view that list.  I 
>>>>> remember using it once where it would list the dependencies and 
>>>>> tell either where they existed, or if they didn't exist, what the 
>>>>> missing file was.  Anyone remember that command? Thanks.
>>>> I use pkg_info -Rr <pkg_name>, where <pkg_name> is the exact name of 
>>>> the package. The -Rr options will tell you what the package depends 
>>>> on, and what depends on the package. To find the exact package name, 
>>>> I do (for example) pkg_info | grep firefox, which returns:
>>>>  firefox-1.5.0.1_1,1 Web browser based on the browser portion of 
>>>> Mozilla
>>>> ...and the I know to do pkg_info -Rr firefox-1.5.0.1_1,1
>>
>> -- 
>> Chris Hill               chris@monochrome.org
>> **                     [ Busy Expunging <|> ]
> 
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe@freebsd.org"
> 


-- 
Regards,
Eric



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44270CF6.1010009>