Alexander E. Patrakov wrote:

> But Debian uses it where appropriate:
> 
> [EMAIL PROTECTED]:~$ ldd /usr/bin/sftp
>         libresolv.so.2 => /lib/i686/cmov/libresolv.so.2 (0xb7f33000)
>         libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 
> (0xb7df2000)
>         libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb7ded000)
>         libz.so.1 => /usr/lib/libz.so.1 (0xb7dd8000)
>         libnsl.so.1 => /lib/i686/cmov/libnsl.so.1 (0xb7dc0000)
>         libcrypt.so.1 => /lib/i686/cmov/libcrypt.so.1 (0xb7d92000)
>         libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0xb7d6a000)
>         libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xb7ce3000)
>         libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xb7cbd000)
>         libcom_err.so.2 => /lib/libcom_err.so.2 (0xb7cba000)
>         libedit.so.2 => /usr/lib/libedit.so.2 (0xb7c9f000)
>         libncurses.so.5 => /lib/libncurses.so.5 (0xb7c5c000)
>         libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7b15000)
>         libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7b11000)
>         libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xb7b08000)
>         libkeyutils.so.1 => /lib/libkeyutils.so.1 (0xb7b05000)
>         /lib/ld-linux.so.2 (0xb7f54000)

Not arguing, but what package is actually linked to libedit (I'm
curious more than anything)? Some folks have the wrong impression
that because something is listed in the output of ldd for a particular
binary, it is used by that binary. That is an incorrect assumption.

For example, just because libedit is listed in ldd output of sftp,
it does *not* mean it is used (not even pulled in directly) by
sftp. It only means that one of *any* of the packages linked to
sftp is linked directly to libedit.

Again, this is not to refute that we must look into the new port
of libedit, I only wrote this as an FYI about the misconception of
what ldd output means.

-- 
Randy

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to