From: Hans-Werner Hilse <hilse@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT - Is there a gcc-4.1.1 alternative?
Date: Sat, 13 Jan 2007 21:45:19 +0100 [thread overview]
Message-ID: <20070113214519.f19670a4.hilse@web.de> (raw)
In-Reply-To: <200701131229.09898.randy@electronsweatshop.com>
Hi,
On Sat, 13 Jan 2007 12:29:09 -0500
Randy Barlow <randy@electronsweatshop.com> wrote:
> On Saturday 13 January 2007 09:42, Michael Sullivan wrote:
> > This strace doesn't help me much. What does "attached" mean, anyway?
>
> I don't know what the problem is, but I can tell you that strace "attaches" to
> a process meaning that it begins to watch the process to see what system
> calls it is making. If the process doesn't make any system calls, then you
> won't see anything with strace. [...]
I think since the suggestion of using "strace" to look if a certain
process is "doing" things was mine. So I owe this thread a bit more
input. Randy, you're completely right. And especially the compile task
in question, "gcc -o insn-attrtab.o" (shortened), is rather CPU- but
not kernel-intensive. I don't know what exactly it does (not familiar
with gcc internals), but it _heavily_ depends on the optimization
level. So my suggestion to the OP would be to carefully look at the
CFLAGS. Maybe -- please correct me if that is the case -- is a gcc
build restricted to certain CFLAGS, though. At this stage, I would
exclude a race condition involving the kernel, e.g. some stale or
missing files. It may have to do with threading, but gcc doesn't thread.
Question to the OP: What is the larger context of that gcc build? A
simple update? A larger scale configuration change?
-hwh
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-13 20:48 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 [this message]
2007-01-13 19:06 ` Bo Ørsted Andresen
2007-01-13 23:05 ` John Blinka
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=20070113214519.f19670a4.hilse@web.de \
--to=hilse@web.de \
--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