From: John Blinka <jblinka@neo.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT - Is there a gcc-4.1.1 alternative?
Date: Sat, 13 Jan 2007 18:05:40 -0500 [thread overview]
Message-ID: <45A965C4.6040602@neo.rr.com> (raw)
In-Reply-To: <1168699369.14521.15.camel@camille.espersunited.com>
Michael Sullivan wrote:
> I'm fed up with this. I've restarted the emerge of gcc-4.1.1-r3 on my
> server box four times now. It always gets to compiling insn-attrtab.o
> and then it never stops. I even went into the Makefile to find the
> exact command used to compile this particular object file and ran the
> command manually. It only took half an hour, but when I told it to
> emerge sys-devel/gcc, I guess it didn't like my manually built file, so
> it's doing it over again. This time it's been trying to build this file
> for over eight hours.
>
> 4499 root 18 0 132m 35m 416 R 1.5 60.2 8:41.94 cc1
>
> bullet ~ # strace -p 4499
> Process 4499 attached - interrupt to quit
>
> This strace doesn't help me much. What does "attached" mean, anyway?
> Is there some other way for me to get gcc-4 on my server box? Some
> binary package for an i586 maybe?
>
You don't mention what sort of machine your server is, but if it's as
old as an i586 then,
in my experience with an old box with very little memory, compiling
insn-attrb takes a
very long time. My 150 mhz laptop takes days to compile gcc and seems
to get stuck
on insn-attrb for many hours. It's been grinding away most of today in
insn-attrb and
has accumulated a couple of hours of cpu time in the process. It'll
probably be
done by Monday or Tuesday.
Just start the emerge then go away and ignore it. It'll finish eventually.
John Blinka
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-13 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 14:42 [gentoo-user] OT - Is there a gcc-4.1.1 alternative? Michael Sullivan
2007-01-13 16:10 ` [gentoo-user] " James
2007-01-13 17:29 ` [gentoo-user] " Randy Barlow
2007-01-13 20:45 ` Hans-Werner Hilse
2007-01-13 19:06 ` Bo Ørsted Andresen
2007-01-13 23:05 ` John Blinka [this message]
2007-01-14 7:39 ` PaulNM
2007-01-14 16:47 ` Dan
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=45A965C4.6040602@neo.rr.com \
--to=jblinka@neo.rr.com \
--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