Bug#332824: synlink strangeness with chroot

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

Jonathan Brandmeyer <jbrandmeyer@earthlink.net> writes:

> Cross-posting to the BTS since its relevant to this bug, and might lead
> to closing it out.
>
> I am running a Debian Sid AMD64 root partition alongside a full Sid i386
> partition.  Right now, the 32-bit partition is used mostly as a chroot
> to run openoffice and mplayer, using the directions on the Debian AMD64
> howto.  I also use it as a full desktop install as a backup.
>
> All of my "partitions" are managed using LVM.  vgchange, which is used
> to initialize LVM in an initramfs, depends on libncurses.so.5 (the
> binary for vgchange is actually located at /lib/lvm-200/lvm).
>
> When you follow the FAQ directions to add an ia32 chroot's lib
> directories to /etc/ld.so.conf[1], ldconfig causes vgchange's dependency
> on libncurses.so.5 to appear to be satisfied using
> $(chroot_path)/usr/lib/libncurses.so.5[2], which is itself a symlink.

Is that symlink absolut and thereby broken? It should only fullfill
the 32bit needs and should not show up for 64bit binaries.

> Weirdly, file -L /mnt/root32/usr/lib/libncurses.so.5 prints
> ... ELF 64-bit LSB shared object, AMD x86-64 ...

Which would indicate it links to /lib/libncurses.so* instead of
../../lib/libncurses.so*. This might be a more common problem.


I wouldn't use the chroot in the ld.so.conf. Use ia32-libs for the
basics and dchroot for bigger stuff.

MfG
        Goswin