| 1 |
> -----Original Message----- |
| 2 |
> From: Graham Murray [mailto:graham@×××××××××××.uk] |
| 3 |
> |
| 4 |
> I do not think it will be that simple. The problem is that once you |
| 5 |
> chroot to /mnt/gentoo all subsequent commands (including emerge and |
| 6 |
gcc) |
| 7 |
> will be looking for /lib/libc.so.6 and /lib/ld-linux.so.2 neither of |
| 8 |
> which will be present following an unmerge of glibc. |
| 9 |
|
| 10 |
This is true. After booting from a CD, |
| 11 |
|
| 12 |
chroot /mnt/gentoo /bin/bash |
| 13 |
|
| 14 |
does not work. |
| 15 |
|
| 16 |
> If you have a binary glibc package, then you could untar it into |
| 17 |
> /mnt/gentoo while booted from the CD. Otherwise I suspect that you |
| 18 |
will |
| 19 |
> either have to find a binary glibc package on the internet or rebuild |
| 20 |
> your system from a stage3 tarball in the usual way. |
| 21 |
|
| 22 |
Indeed the solution was to build glibc-2.6.1.tbz2 with quickpkg on |
| 23 |
another machine (luckily I had one) and scp into the damaged machine |
| 24 |
when booted from the CD. Then copying all the files into their |
| 25 |
respective places inside /mnt/gentoo/... |
| 26 |
Also need to check symbolic links etc. Not a pleasant work. |
| 27 |
|
| 28 |
Then chroot /mnt/gentoo /bin/bash finally works. After that, an emerge |
| 29 |
of glibc solves the problem. |
| 30 |
|
| 31 |
Thanks for the inputs. |
| 32 |
|
| 33 |
-- |
| 34 |
Valmor |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-user@g.o mailing list |
Archives