At Sun, 11 Dec 2005 02:35:01 -0600 Roy Wright <[EMAIL PROTECTED]> wrote:
> Allan Gottlieb wrote: > >>After upgrading gcc I did the safer post-installation, >> emerge -e system >> emerge -e world >> >>The first went fine. The second died after about 300 emerges and >>printed >> >> making executable: /usr/lib/libgtkhtml-1.1.so.3.0.5 >> >>> Completed installing gtkhtml-1.1.10-r1 into >> /var/tmp/portage/gtkhtml-1.1.10-r1/image/ >> >> --------------------------- ACCESS VIOLATION SUMMARY >> --------------------------- >> LOG FILE = >> "/var/log/sandbox/sandbox-gnome-extra_-_gtkhtml-1.1.10-r1-32251.log" >> >> open_wr: /usr/share/gnome/html/gtkhtml/gtkhtml-gtkhtml-enums.html.new >> >> -------------------------------------------------------------------------------- >> ajglap ~ # >> > Check your disk space. I hit the same problem and was out of space on > root... > /var/logs got slashed. > /var/tmp/portage got bound to a different drive > /var/cache/http-replicator got bound to a different drive > > Seems to require about 6GB of free space on root for my system... > > Sometimes emerge --resume works, sometimes it doesn't. Haven't figured > this out yet. Currently at 318 of 1046 on emerge -e world... The disk space was fine for these builds. Apparently this is a know problem, see bug #114399. A workaround was given unmerge gtkhtml unmerge libgtkhtml remove any gtkhtml and gtkhtml from /var/tmp/portage emerge gtkhtml and libgtkhtml This did fix it for me. However, I had already done an emerge --resume --skipfirst so the newly built [lib]gtkhtml (with gcc 3.4) were not available for the remainder of my emerge -e world. I also had some small problems with synaptics (I forget the problem) and firefox (corrupted distfile). Those two problems were easy to fix and the emerge -e world has finished. For "cleanliness" I am running another emerge -e world to see if it can go all the way through without any problems. (I have run emerge depclean and revdep-rebuild.) allan -- [email protected] mailing list
