On 8/31/05, Tushar Teredesai <[EMAIL PROTECTED]> wrote: > Sorry for the late reply, still going thru some old mail that I > received while on vacation. > > On 8/25/05, Randy McMurchy <[EMAIL PROTECTED]> wrote: > > > > ldd in-of-itself is no indication that a package is actually a > > dependency. Libtiff could have easily been called into the build > > because it was a library dependency of some *other* package that > > was used in the build. Then libtiff would show up in ldd, but > > never actually was a direct dependency of the package being built. > > As Matt said, readelf is a good way of knowing. Though it won't tell > you if the dependency is a required one or an optional one.
Forgot to add, I also use strace to determine "executable" dependencies. -- Tushar Teredesai mailto:[EMAIL PROTECTED] http://www.linuxfromscratch.org/~tushar/ -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
