From: Janis Johnson <janis187@us.ibm.com>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: gcc@gcc.gnu.org, linux-kernel@vger.kernel.org,
schwidefsky@de.ibm.com, ak@suse.de
Subject: Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
Date: Thu, 1 Apr 2004 13:13:48 -0800 [thread overview]
Message-ID: <20040401211348.GA5739@us.ibm.com> (raw)
In-Reply-To: <200404011928.VAA23657@faui1d.informatik.uni-erlangen.de>
On Thu, Apr 01, 2004 at 09:28:20PM +0200, Ulrich Weigand wrote:
> Hello,
>
> I'm seeing a race condition on Linux 2.6 that rather reproducibly
> causes GCC bootstrap failures on current mainline.
We saw lots of parallel build problems when using a 2.6 kernel on
an older distribution. The problems went away when we used 'make'
built with a new version of glibc.
Janis
next prev parent reply other threads:[~2004-04-01 21:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 19:28 Linux 2.6 nanosecond time stamp weirdness breaks GCC build 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20040401211348.GA5739@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=ak@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=weigand@i1.informatik.uni-erlangen.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.