On 04/02/2015 05:34 PM, Szabolcs Nagy wrote:
> * Jean-Marc Pigeon <jmp@safe.ca> [2015-04-02 16:40:22 -0400]:
>> Using ldd was the best way I found to list one package all
>> dependencies (looking at ELF file type ans searching for
>> required external components).
>> If you have a better way (more standard) to propose not using
>> ldd that will be a good thing. idea?
> 
> if you care about the elf dependencies then use the elf standard
> 
> an elf binary will have its dependencies in the dynamic section
> (DT_NEEDED entries, you can get them by readelf -d or objdump -p)
> 
> (of course the names there are mapped to paths in an implementation
> defined way and will depend on the runtime environment)
> 
Good idea, I tried to use readelf to do this (few month ago)
but it was not providing the full path. That's why I
decided to use ldd (was in hurry).
I need to redo the function using readelf in a smarter
way. Thanks.


-- 

A bientôt
===========================================================
Jean-Marc Pigeon                        E-Mail: jmp@safe.ca
SAFE Inc.                             Phone: (514) 493-4280
  Clement, 'a kiss solution' to get rid of SPAM (at last)
     Clement' Home base <"http://www.clement.safe.ca">
===========================================================