On Tue, Jul 05, 2011 at 12:15:59PM +0200, Sven Joachim wrote: > On 2011-07-04 22:18 +0200, Aurelien Jarno wrote: > > > Up to know libc6 is providing a /lib64 -> /lib symlink on amd64, > > kfreebsd-amd64, ppc64 and sparc64. With multiarch it's not possible for > > libc6 to provide such a symlink anymore as the package can be installed > > (using multiarch) on a 32-bit system. See bug#632176 for more details. > > > > It looks like the best place to place such a symbolic link is in > > base-files. Could you please provide it in base-files for the above > > architectures? For that you need to add a Replace: libc6 (<< 2.13-10) > > (to be adjusted to the current libc6 version). When done, I'll remove > > the symlink from libc6 and add the necessary dependencies. > > The more I think about this, the more it confuses me. Even if libc6 > Pre-Depends on base-files, does that guarantee that libc6 is unpacked > after base-files while bootstrapping a system? That would be necessary > if you want to put ld-linux-x86-64.so.2 into /lib64.
ld-linux-x86-64.so.2 is currently in /lib and there is no plan to change that. During bootstrapping, all the packages are first unpacked, and then installed using dpkg. This last step will already have the correct /lib64 -> /lib symlink. > If that is not your plan, how are amd64 binaries supposed to work when > all you have is /lib/ld-linux-x86-64.so.2 and no /lib64 symlink to it > (on foreign architectures)? > That's a good plan, it looks like we definitely have to move ld-linux-x86-64.so.2 from /lib to /lib64. Looks like a complex transition. -- Aurelien Jarno GPG: 1024D/F1BCDB73 [email protected] http://www.aurel32.net -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
