[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems update libc6



"Hans-J. Ullrich" <hans.ullrich@loop.de> writes:

> Hello all,
> I had slight problems to upgrade to libc6-2.3.6-8 as this package did not want 
> to install. Hereby I have a slight understanding problem. Can someone 
> explain, what now is the correct way ?
>
> Short description:
>
> I have a chroot, as described on the debian-AMD64 site. There you wrote:
>
> "You also need a link to your 32bit linker in the /lib path. Change in to 
> directory /lib and create a link to the 32bit linker library of your chroot: 
> (The name of the 64bit linker is ld-linux-x86-64.so.2)"
>
> I did so, when I first installed this computer.

Don't do that. Just install ia32-libs (sarge) or libc6-i386 (etch/sid)
which contain the linker. You probably end up with them installed
anyway for some reason and then the link can only confuse matters.

> Now to upgrade libc6 I had to delete this link, otherwise I could not install 
> the new libc6, and, now the link does not point any more 
> to /var/chroot/sid-ia32/lib/libc-2.3.6 any more, but to /lib/libc-2.3.6-8.

I heard about the libc6 complaining with the manual linking but since
I never did that I never saw it myself. Using the ia32-libs or
libc6-i386 package has no such effect.

> Is this information on the AMD64-site deprecated ?

Just in needs of slight improvements.

> For your information, here the relevant links
>
> 4505604    0 lrwxrwxrwx  1 root root      11 2006-03-12 19:57 ld-linux-so.2 -> 
> ld-2.3.6.so
> 4505603    0 lrwxrwxrwx  1 root root      11 2006-05-19 14:54 
> ld-linux-x86-64.so.2 -> ld-2.3.6.so
> 4505759    0 lrwxrwxrwx  1 root root      25 2006-05-02 09:28 
> ld-lsb-x86-64.so.3 -> /lib/ld-linux-x86-64.so.2
>
>
> I want to run 32-bit and 64-bit programs. How is the status now ?
>
> Is chroot still needed ? Should I use chroot any more because it is easier to 
> manage ? 

You can run 32bit programs with ia32-libs. But if you want to use
apt-get to install 32bit programs then you need a chroot. It depends
on what you want to do.

> Please help me to understand the policy after this.
>
> Thanks and best regards
>
> Hans

MfG
        Goswin



Reply to: