public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/31840]  New: race condition in makefiles
Date: Sat, 05 May 2007 12:54:00 -0000	[thread overview]
Message-ID: <bug-31840-11013@http.gcc.gnu.org/bugzilla/> (raw)

I have not tried this on a single core, but on 2 or more core machines, a
bootstrap will fail if you issue the following commands:

make clean
make -j4

This assumes that the bootstrap has been built at least once before the make
clean.  When it fails, it can be restarted with make -j4 and it will most times
run to conclusion.  Builds also sometimes fail going from one stage to the
next, but this may be the same problem.  

I know that this fails in at r124381 and has been doing this for at least a
week or so.  

I have not tried this on a single core machine, i do not use higher than j2 on
those and the problem does not seem to arise with j1 or j2.

my configure string is generally --enable-languages=c,c++,fortran
--disable-multilib (if appropriate)


-- 
           Summary: race condition in makefiles
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: zadeck at naturalbridge dot com
 GCC build triplet: same
  GCC host triplet: ppc, x86-64, ia-32 on linux
GCC target triplet: same


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31840


                 reply	other threads:[~2007-05-05 12:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-31840-11013@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).