Peter B. Steiger wrote these words on 06/01/06 13:40 CST:
> You probably already know this, but for those who don't... ldd is your
> friend. When a specific binary (such as /usr/bin/acroread) fails, type:
> ldd /usr/bin/acroread
>
> ... and look for any libraries it says it can't find.
> [snip rest of explanation]
Just so others get the big picture, what Peter is saying is generally
true. However, there are exceptions. Take Firefox for example, say
you're having problems with it and you take Peter's advice. You will
be pulling your hair out trying to fix what isn't broken.
Notice below there are several libs Firefox "can't find". However,
it runs perfectly because it has internal knowledge of the whereabouts
of the libs.
[EMAIL PROTECTED]: ~/build > ldd /opt/firefox/lib/firefox*/firefox-bin
linux-gate.so.1 => (0xffffe000)
libmozjs.so => not found
libxpcom.so => not found
libxpcom_core.so => not found
libplds4.so => /usr/lib/libplds4.so (0xb7ef7000)
libplc4.so => /usr/lib/libplc4.so (0xb7ef2000)
libnspr4.so => /usr/lib/libnspr4.so (0xb7ec0000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7eac000)
libdl.so.2 => /lib/libdl.so.2 (0xb7ea8000)
[snip remaining libraries]
--
Randy
rmlscsi: [bogomips 1003.27] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
13:46:00 up 20 days, 5:46, 1 user, load average: 0.13, 0.05, 0.01
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
