| 1 |
> > library, but after the upgrade of glibc it shows up in /usr/lib. The |
| 2 |
> > only solution I could make up was to move everything from /usr/lib |
| 3 |
> > to /usr/lib64, symlink /usr/lib -> /usr/lib64 and then start emerging |
| 4 |
> |
| 5 |
> Actually seems like bug #133547, in which case it seems like you did |
| 6 |
> the right thing to fix. This bug seems to be fixed in |
| 7 |
> baselayout-1.12.0 (see /usr/portage/sys-apps/baselayout/ChangeLog), |
| 8 |
> but unfortunately both 1.12.0-r1 and 1.12.1 are still ~amd64. So what |
| 9 |
> you may need to do before updating gcc or glibc is: |
| 10 |
> |
| 11 |
> echo "<=sys-apps/baselayout-1.12.99 ~amd64" >>/etc/portage/package.keywords |
| 12 |
> emerge -u baselayout |
| 13 |
|
| 14 |
I followed this recipe - (a fresh --sync'd system) -> 'emerge portage' -> |
| 15 |
'emerge baselayout' (1.12.1) -> 'emerge gcc glibc' - and I'm stuck again, |
| 16 |
with the same problem. At any rate, thank you for your reply. |
| 17 |
|
| 18 |
-Roman |
| 19 |
-- |
| 20 |
gentoo-user@g.o mailing list |
Archives