That bug is a tricky one. Explanation for other readers: musl libc has no standalone ldd as glibc has. Instead it uses /lib/ld-musl-*.so.1 as runtime and ldd. The suggested way by the musl folks is to create a local symlink e.g. 'ln -s /lib/ld-musl-x86_64.so.1 ldd'. By running the symlink named ldd, the executable switches to the ldd mode and outputs the linked objects of the target executable.
I will discuss this problem upstream. In the worst case i will provide a simple C programm wrapper, that will execute /lib/ld-musl-*.so.1 and overwrite argv[0] in a non standard way. Until the bug is fixed, see: http://wiki.musl-libc.org/wiki/FAQ#Q:_where_is_ldd_.3F On Sun, Dec 15, 2013 at 2:12 AM, Shawn Landden <sh...@churchofgit.com> wrote: > > Package: musl > Version: 0.9.14-2 > Severity: normal > > musl's ldd doesn't work unless argv[0] == ldd > > aka ldd is a symlink to musl > > > -- System Information: > Debian Release: jessie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > armhf > > Kernel: Linux 3.13.0-rc3-00330-gca33675 (SMP w/2 CPU cores; PREEMPT) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > -- no debconf information
