From: Paul Jackson <pj@sgi.com>
To: Ben Greear <greearb@candelatech.com>
Cc: greearb@candelatech.com, linux-kernel@vger.kernel.org
Subject: Re: Compile error with 2.6.15
Date: Fri, 13 Jan 2006 12:34:15 -0800 [thread overview]
Message-ID: <20060113123415.932b4a80.pj@sgi.com> (raw)
In-Reply-To: <43C76104.5090607@candelatech.com>
> Guess it is probably not a real problem...
Or, it's probably a real problem. The asm-offsets.h file
has a long history of being a thorn in the side of Makefiles,
including race conditions (such as you saw with -j4). There
is a natural circular dependency in the construction of the
asm-offsets.h file and the rest of the build that's tricky
to get right.
Whether or not someone sees enough evidence yet to deal with
this instance of that breakage ... that's another matter.
Often this kind of breakage remains until someone with the
right mental weapons gets bit by it, and goes hunting it down.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2006-01-13 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 7:56 Compile error with 2.6.15 Ben Greear
2006-01-13 8:12 ` Ben Greear
2006-01-13 20:34 ` Paul Jackson [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=20060113123415.932b4a80.pj@sgi.com \
--to=pj@sgi.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.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