3 ms·
Yes. So is the (IMHO) best workaround of using lddtree (pax-utils) instead. Available on pretty much all distros, though probably not installed by default.
by eqvinox 3y ago
Yes. So is the (IMHO) best workaround of using lddtree (pax-utils) instead. Available on pretty much all distros, though probably not installed by default.
- anthk 3y agoobjdump -x /path/to/bin | grep NEEDED
- eqvinox 3y agoDoesn't tell you if/where the library is found on your system.
- janAkali 3y agofor i in $(objdump -p /path/to/bin | grep NEEDED | awk '{print $2}'); do ldconfig -p | awk -v var="$i" '$1==var{print $0}'; done edit: even simpler, for i in $(objdump -p /path/to/bin | grep NEEDED | awk '{print $2}'); do ldconfig -p | grep $i; done
- eqvinox 3y agoCool, but I think I'll stick to lddtree ;) (… it also recurses down on the dependencies, presumably you can extend your shell script to do that too but at some point why not just use the existing tools?)