Package: fakechroot
Version: 2.16-1
Severity: normal
Tags: patch
Dear Maintainer,
ldd gives a different result wrt ld-linux-x86-64.so.2 when invoked
inside or outside of the fakechroot environment :
ldd my_wheezy_fakechroot/bin/kmod
linux-vdso.so.1 => (0x00007fff50dff000)
libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x00007f35e52c7000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f35e4f3d000)
/lib64/ld-linux-x86-64.so.2 (0x00007f35e56f8000)
fakeroot -i .fakeroot_state fakechroot chroot my_wheezy_fakechroot/ ldd
/bin/kmod
linux-vdso.so.1 => (0x0000000000000000)
libfakechroot.so libfakeroot-sysv.so => not found
libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x0000000000000000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x0000000000000000)
/lib/ld-linux-x86-64.so.2 (0x0000000000000000)
/lib64 seems to be a directory in wheezy, not a symlink to /lib as in squeeze
ls -AlFd /lib64
drwxr-xr-x 2 root root 60 févr. 4 22:47 /lib64/
ls -AlF /lib64
total 0
lrwxrwxrwx 1 root root 32 févr. 17 16:19 ld-linux-x86-64.so.2 ->
/lib/x86_64-linux-gnu/ld-2.13.so*
I don't know if similar issues occur on mips64, ppc64 and sparc64.
Could the following patch help ?
Regards,
JH Chatenet
diff -Naur a/usr/bin/ldd.fakechroot b/usr/bin/ldd.fakechroot
--- a/usr/bin/ldd.fakechroot 2013-02-17 17:06:30.608261517 +0000
+++ b/usr/bin/ldd.fakechroot 2013-02-17 18:01:36.096262102 +0000
@@ -77,6 +77,9 @@
push @Libs, 'linux-vdso.so.1';
$Libs{'linux-vdso.so.1'} = '';
}
+ if ($Format =~ /^elf64-x86-64/) {
+ $Ldsodir = "/lib64";
+ }
else {
push @Libs, 'linux-gate.so.1';
$Libs{'linux-gate.so.1'} = '';
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages fakechroot depends on:
ii libfakechroot 2.16-1
fakechroot recommends no packages.
fakechroot suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
