Re: Some binaries using /lib/ld.so instead of /lib64/ld.so

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Laurent Bonnaud <bonnaud@lis.inpg.fr> writes:

> Hi,
>
> And indeed:
>
> $ ldd /usr/bin/less |grep ld
>         /lib/ld-linux-x86-64.so.2 (0x0000003b3cc00000)
>
> whereas all other binaries on the system use this:
>
> $ ldd /bin/ls |grep ld
>         /lib64/ld-linux-x86-64.so.2 (0x0000003b3cc00000)
>
> Of course, both ld.so versions are the same, but:
>
>  - this inconsistency may be the result of a more serious problem
>  - I like all binaries on my system to be consistent :>.
>
> Is this something the kind AMD64 porters could fix or should I send bug
> reports for the concerned packages ?

Under sarge and sid I get the following:

% ldd /usr/bin/less
        libncurses.so.5 => /lib/libncurses.so.5 (0x0000002a9566c000)
        libc.so.6 => /lib/libc.so.6 (0x0000002a957c5000)
        /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x0000002a95556000)

% madison less
      less |      382-1 |        stable | source, amd64
      less |      382-2 |       testing | source, amd64
      less |      382-2 |      unstable | source, amd64

Package: less
Version: 382-1
Depends: libc6 (>= 2.3.2.ds1-4), libncurses5 (>= 5.4-1), debianutils (>= 1.8)

Package: less
Version: 382-2
Depends: libc6 (>= 2.3.2.ds1-4), libncurses5 (>= 5.4-1), debianutils (>= 1.8)

Both less versions are compiled with the same libc and ld. Where does
your less come from?

MfG
        Goswin