Summary: | emerge fails with error after upgrading portage, gcc and glibc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Humphrey <peter> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED CANTFIX | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Humphrey
2004-06-09 17:57:34 UTC
I should have included the following entries from /var/log/emerge.log, which followed the excerpt I did give. emerge evidently wasn't failing until after these further updates: 1086819634: >>> starting rsync with rsync://134.147.32.57/gentoo-portage 1086819756: >>> emerge (1 of 5) x11-terms/xterm-191 to / 1086821556: >>> emerge (1 of 4) app-office/koffice-1.3.1-r1 to / 1086822331: >>> emerge (1 of 3) dev-util/cvs-1.11.17 to / 1086822681: >>> emerge (2 of 3) app-text/aspell-0.50.5-r1 to / 1086822758: >>> emerge (3 of 3) media-video/ffmpeg-0.4.8.20040322-r1 to / After that, emerge failed as described, and after a reboot kdm could not start KDE either, so I issued emerge commands at a virtual terminal. I can't fix KDE until I've fixed emerge. Reopen with output from emerge --info please. As I have already said, I cannot run emerge at all. How else can I help? ayanami rxvt-unicode # readelf -s /lib/libpthread.so.0 | grep libc_fork 269: 0000000000000000 71 FUNC GLOBAL DEFAULT UND __libc_fork@GLIBC_PRIVATE (7) looks like libc_fork is now an @GLIBC_PRIVATE symbol... other than recompiling python on another machine/install and transferring it over or using quickpkg from within a recent stage3 tarball, i have no idea how to help here. I just upgraded my system and I have the same problem. Did you find any solution since the last post? |