From: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
To: Joe.Buck@synopsys.com (Joe Buck)
Cc: ak@suse.de (Andi Kleen),
weigand@i1.informatik.uni-erlangen.de (Ulrich Weigand),
gcc@gcc.gnu.org, linux-kernel@vger.kernel.org,
schwidefsky@de.ibm.com
Subject: Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
Date: Fri, 2 Apr 2004 00:48:55 +0200 (CEST) [thread overview]
Message-ID: <200404012248.AAA23951@faui1d.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20040401143908.B4619@synopsys.com> from "Joe Buck" at Apr 01, 2004 02:39:08 PM
Joe Buck wrote:
> Case 2: make falsely thinks that the .c is younger than the .o. It
> recompiles the .c file, even though it didn't have to. Harmless.
*Not* harmless, in fact this is exactly what breaks my bootstrap.
Think about what happens when cc1 is 'harmlessly' rebuilt just
while in a parallel make that very same cc1 binary is used to
run a compile ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
weigand@informatik.uni-erlangen.de
next prev parent reply other threads:[~2004-04-01 22:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 19:28 Ulrich Weigand
2004-04-01 20:09 ` Andi Kleen
2004-04-01 20:39 ` Daniel Jacobowitz
2004-04-01 20:46 ` Andi Kleen
2004-04-01 21:01 ` Ulrich Weigand
2004-04-01 21:44 ` Andi Kleen
2004-04-01 22:39 ` Joe Buck
2004-04-01 22:44 ` Paul Jarc
2004-04-01 22:48 ` Ulrich Weigand [this message]
2004-04-01 23:58 ` Joe Buck
2004-04-02 0:13 ` Daniel Jacobowitz
2004-04-02 0:02 ` Jamie Lokier
2004-04-02 0:35 ` Paul Eggert
2004-04-02 1:14 ` Jamie Lokier
2004-04-02 7:57 ` James H. Cloos Jr.
2004-04-02 9:22 ` Paul Eggert
2004-04-02 16:23 ` Jamie Lokier
2004-04-02 20:45 ` Paul Eggert
2004-04-02 21:07 ` Jamie Lokier
2004-04-02 21:56 ` Paul Eggert
2004-04-03 4:59 ` Andrew Pimlott
2004-04-02 0:37 ` Andrew Morton
2004-06-07 16:03 ` Jörn Engel
2004-04-01 21:13 ` Janis Johnson
2004-04-01 21:41 ` Ulrich Weigand
2004-04-02 0:30 ` Alan Modra
2004-04-02 9:05 ` P
2004-04-02 17:27 ` Alexandre Oliva
2004-04-01 20:51 Michael Elizabeth Chastain
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=200404012248.AAA23951@faui1d.informatik.uni-erlangen.de \
--to=weigand@i1.informatik.uni-erlangen.de \
--cc=Joe.Buck@synopsys.com \
--cc=ak@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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
all inboxes | Powered by JetHome®