Bug#316453: found a "not-so-bad" solution

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

Pascal Giard <evilynux@gmail.com> writes:

>> Under Debian /lib64 is a link to /lib.
>
> yes i know, i was also surprised to see that it was working by adding
> /lib to LD_LIBRARY_PATH in the mkinitrd.conf.
>
>> /lib64/ld-linux-x86-64.so.2 has
>> to exist. Your change should have no effect at all as LD_LIBRARY_PATH
>> is usualy unset and /lib is already in the default path.
>
> well, in my case, my /etc/ld.so.conf was:
> /lib64
> /usr/lib
> /usr/lib64
> /usr/X11R6/lib
> /usr/X11R6/lib64
> /usr/local/lib/
> # chroot 32bit
> /home/chroot-sid-i386/lib
> /home/chroot-sid-i386/usr/lib
> /home/chroot-sid-i386/usr/X11R6/lib
> /home/chroot-sid-i386/usr/local/lib/
>
> i changed it by prepending /lib and now it works w/o modifying the
> mkinitrd.conf.
> unfortunatly, i can't remember if /lib was ever there or if it was i
> who removed it accidently at one point.
>
>> Caoul you add a "set -x" to /usr/sbin/mkinitrd, reinstall the
>> kernel-image and send us a log of the output please.
>
> yes, here it is anyway...even if we know the root now...
> libc.so.6 is the cornerstone, so look at it's location to compare.
>
> -Pascal

Just a though: Ubuntu?

MfG
        Goswin