linux fan wrote: > On 11/23/09, Bruce Dubbs <bruce.du...@gmail.com> wrote: > >> To check things out a little more, you can try > > Er, uh, excuse my dumbness, but ... > did you mean like: > ldd /usr/bin/make
Sorry. I did cd /usr/bin first. > or like: > ldd /tools/bin/make > > or like: > /tools/bin/ldd /tools/bin/make > > ... By the way, this is without the stripping ... > > /tools/bin/ldd /tools/bin/make > linux-gate.so.1 => (0xffffe000) > librt.so.1 => /tools/lib/librt.so.1 (0xb7745000) > libgcc_s.so.1 => /tools/lib/libgcc_s.so.1 (0xb7727000) > libc.so.6 => /tools/lib/libc.so.6 (0xb75d0000) > libpthread.so.0 => /tools/lib/libpthread.so.0 (0xb75b5000) > /tools/lib/ld-linux.so.2 (0xb774f000) > > file /tools/bin/make > /tools/bin/make: ELF 32-bit LSB executable, Intel 80386, version 1 > (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, > not stripped > ... Or did you want me to get it sripped and then ... > but help me know EXACT command to use, thanks This look OK. What do they look like after stripping? If you are running a tool on a file you can use the absolute path or a relative path. I just used a relative path. You used an absolute path. Either works. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
