From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] nslu2 non turbo slug emerge gcc freezes / locks up
Date: Tue, 11 Jul 2006 08:37:12 -0400 [thread overview]
Message-ID: <1152621432.30124.141.camel@localhost> (raw)
In-Reply-To: <44B291EA.6060204@mchsi.com>
You should of started a new thread for this vs hijacking a sub thread of
somebody else's.
On Mon, 2006-07-10 at 12:44 -0500, nick thompson wrote:
> hi all,
> I have a nslu2 (non-turbo, "slug") and I have everything up to date
> except gcc freezes when untarring the tar.bz2, and I have let it sit for
> hours and hours, even overnight, and it sure seems frozen to me. Anyone
> seen this?
Yes I have in the exact same spot. Sadly I never found a solution for
that problem. Seems to me that the kernel hates on large file i/o.
Perhaps try unpacking it elsewhere and net mounting it.
or.. build a cross native compiler for armeb.
good luck.
> Nick
>
> "All unix, all the time."
>
> http://npt.ath.cx
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-11 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 11:05 [gentoo-embedded] Problem cross compiling modular X Ryan Baldwin
2006-07-06 12:02 ` Ryan Baldwin
2006-07-06 14:37 ` Ryan Baldwin
2006-07-06 19:21 ` Mike Frysinger
2006-08-24 19:19 ` Enrico Weigelt
2006-08-24 20:31 ` Leonardo Shiguemi Dinnouti
2006-08-28 6:51 ` Peter S. Mazinger
2006-08-24 19:17 ` Enrico Weigelt
2006-08-25 3:39 ` Mike Frysinger
2006-07-10 10:41 ` Peter S. Mazinger
2006-07-10 11:01 ` Ryan Baldwin
2006-07-10 17:44 ` [gentoo-embedded] nslu2 non turbo slug emerge gcc freezes / locks up nick thompson
2006-07-11 12:37 ` Ned Ludd [this message]
2006-07-14 3:40 ` nick thompson
2006-07-15 2:39 ` Mike Frysinger
2006-07-14 20:21 ` [gentoo-embedded] Problem cross compiling modular X Chuck Robey
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=1152621432.30124.141.camel@localhost \
--to=solar@gentoo.org \
--cc=gentoo-embedded@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