where did ldd go?
Erh, there used to be something called ldd, right? For finding out which dynamic libs an executable linked against? It's gone! Where do I get it? Where is there a map of binary names to debs? -chris
Re: where did ldd go?
On Sun, Oct 29, 2000 at 02:33:06AM -0800, Krzys Majewski wrote: Erh, there used to be something called ldd, right? For finding out which dynamic libs an executable linked against? It's gone! Where do I get it? Where is there a map of binary names to debs? -chris This doesn't help if it's not in your path, but: $ dpkg -S `which ldd` libc6: /usr/bin/ldd Are there other signs that glibc is broken on your system? Brent -- Would you like to play a game of hide and seek now? If you have X-Ray eyes, promise not to peek now! --The Apples in Stereo Signal in the Sky (Let's Go)
Re: where did ldd go?
This doesn't help if it's not in your path, but: $ dpkg -S `which ldd` libc6: /usr/bin/ldd OK thanks, I used to do this by grepping /var/lib/dpkg/info/* Are there other signs that glibc is broken on your system? Well, I don't know. I pointed apt-get to unstable in order to install something (xmps??), which ended up upgrading my libc and some other stuff (C++ libraries??). This broke something else (undefined symbols in some X libraries when compiling stuff). So I manually downgraded libc (and hopefully all the other things that had been upgraded) via ftp + dpkg. Now I have the stable libc again, but as you suggest, I may have broken something in the process. I've now got ldd from the ldso deb. -chris
