public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anders Thøgersen" <anderslt@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Segfault in emerge
Date: Sun, 21 May 2006 00:35:04 +0200	[thread overview]
Message-ID: <20060520223504.GB9058@genaro.mydomain> (raw)
In-Reply-To: <200605120206.48904.ro-wa@gmx.at>

Hi!

On 02:06 Fri 12 May 2006, Robert Walter wrote:
> On Friday 12 May 2006 01:04, Anders Thøgersen wrote:
> > I am unsure of how to tackle this.  Could it be a hardware problem?
> i guess so :-( maybe ram or net-hardware?
> is it just emerge sync having that problem? 

Sorry for the late reply..

Yes only emerge sync, and emerge --metadata display this problem.  I am
able to compile firefox and other packages with no problem.

> do other applications accessing the net behave strange?

Interesting question.  Last week firefox unexpectedly segfaulted, but
otherwise I have only seen problems with rox and amarok but that was due
to a problem of binary incompatibility between an older gcc and gcc 3.4.

I have decided not to consider this problem as a hardware issue, until I
am out of ideas and suggestions about how to fix my problem.

Thanks,
/Anders
> regards. robert
> 
> -- 
> gentoo-amd64@gentoo.org mailing list
> 
> 

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-05-20 21:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 23:04 [gentoo-amd64] Segfault in emerge Anders Thøgersen
2006-05-12  0:06 ` Robert Walter
2006-05-20 22:35   ` Anders Thøgersen [this message]
2006-05-12  4:52 ` [gentoo-amd64] " Duncan
2006-05-20 22:30   ` Anders Thøgersen
2006-05-21 14:31     ` [gentoo-amd64] " Duncan
2006-05-21 16:11     ` [gentoo-amd64] " Bob Slawson
2006-07-09  3:28       ` Anders Thøgersen
2006-07-09 11:19         ` [gentoo-amd64] " Duncan
2006-07-09 20:32           ` Anders Thøgersen

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=20060520223504.GB9058@genaro.mydomain \
    --to=anderslt@gmail.com \
    --cc=gentoo-amd64@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