Closed ghost closed 10 years ago
Short explanation: it is not a bug it is a feature :) Longer explanation: Debian has moved to so called multiarch system that now only have ld-linux-x86_64.so.2 in /lib64 and all other libs in /lib/x86_64-linux-gnu/ as by default my script cannot see that link (ldconfig -p does not see it there) so i just try creating link and on debian it will point to correct location. On openSUSE it will "fail" which is expected as there is already library in place. So maybe I should add "echo this will fail on non debian" (comment is in script stating that already)
noted. I see the "will fail" comment in the script. thanks.
once IN the chroot, if I exec
ldconfig
it returns
ldconfig: /lib/ld-linux.so.2 is for unknown machine 3.
checking
ls -al /lib/ld-linux.so*
-rwxr-xr-x+ 1 root root 152418 Apr 8 10:52 /lib/ld-linux.so.2
file /lib/ld-linux.so.2
/lib/ld-linux.so.2: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xfa97022309e1748552b2d492f78c1439bbfdc9f5, not stripped
it does NOT seem to interfere with ldconfig execution and its cache creation
rm -f /etc/ld.so.cache
ldconfig
ldconfig: /lib/ld-linux.so.2 is for unknown machine 3.
ls -al /etc/ld.so.cache
-rw-r--r--+ 1 root root 14659 Apr 8 16:18 /etc/ld.so.cache
this
https://bugs.launchpad.net/linaro-aarch64/+bug/1074313
may be relevant ...
i'm closing issue as i hope you agree there is no any issue (maybe only cosmetic) :)
latest pull fixes the fails/aborts. stiff have a symlink issue,
chroot is now funtional,