From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "ACCESS VIOLATION" with emerge -e world
Date: Sun, 11 Dec 2005 13:19:51 -0500 [thread overview]
Message-ID: <yu9lkyr7ayg.fsf@nyu.edu> (raw)
In-Reply-To: <439BE4B5.2040800@cisco.com> (Roy Wright's message of "Sun, 11 Dec 2005 02:35:01 -0600")
At Sun, 11 Dec 2005 02:35:01 -0600 Roy Wright <royw@cisco.com> 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
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-12-11 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 13:35 [gentoo-user] "ACCESS VIOLATION" with emerge -e world Allan Gottlieb
2005-12-11 8:35 ` Roy Wright
2005-12-11 18:19 ` Allan Gottlieb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yu9lkyr7ayg.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox