At Sat, 26 Mar 2005 04:15:59 +0200, George Cristian Birzan wrote: > Output on experimental machine: > [EMAIL PROTECTED]:~$ ldd /bin/bash > linux-gate.so.1 => (0xffffe000) > libncurses.so.5 => /lib/libncurses.so.5 (0xb7f93000) > libdl.so.2 => /lib/tls/libdl.so.2 (0xb7f90000) > libc.so.6 => /lib/tls/libc.so.6 (0xb7e75000) > /lib/ld-linux.so.2 (0xb7fea000) > > Output on sid machine: > [EMAIL PROTECTED]:~$ ldd /bin/bash > libncurses.so.5 => /lib/libncurses.so.5 (0x4001e000) > libdl.so.2 => /lib/tls/libdl.so.2 (0x4005d000) > libc.so.6 => /lib/tls/libc.so.6 (0x40061000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > > So far, this hit me in the face by breaking mkinitrd but it will also > break other scripts which depend on that.
I expect you to explain why mkinitrd breaks with new ldd. > Fixing mkinitrd would be relatively easy, I guess, since I fixed mine, > but there may be other scripts which depend on this behaviour. But this argument does not become the exact reason to modify ldd. I think tools should be followed because the behavior of ldd is not standardized. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
