From: Ingo Molnar <mingo@elte.hu>
To: git@vger.kernel.org
Subject: [spurious parallel build bug] make -j fails with: "mv: mv: cannot stat `perl.mak': No such file or directory"
Date: Mon, 27 Apr 2009 11:48:43 +0200 [thread overview]
Message-ID: <20090427094843.GA5849@elte.hu> (raw)
I got this when i built v1.6.3-rc3 for the first time:
$ make -j
[...]
CC builtin-annotate.o
CC builtin-apply.o
CC builtin-archive.o
CC builtin-bisect--helper.o
mv: mv: cannot stat `perl.mak': No such file or directory
mv: cannot stat `perl.mak': No such file or directory
CC builtin-blame.o
mv: cannot stat `perl.mak': No such file or directory
mv: cannot stat `perl.mak': No such file or directory
cannot stat `perl.mak': No such file or directory
a plain 'make' worked.
Interestingly, a second attempt to reproduce it after a 'make clean'
failed to trigger the bug. So it's either timing sensitive or
there's some other weirdness that caused this.
Ingo
next reply other threads:[~2009-04-27 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 9:48 Ingo Molnar [this message]
2009-04-27 17:01 ` [spurious parallel build bug] make -j fails with: "mv: mv: cannot stat `perl.mak': No such file or directory" Junio C Hamano
2009-04-27 18:34 ` Ingo Molnar
2009-04-27 20:19 ` Jeff King
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=20090427094843.GA5849@elte.hu \
--to=mingo@elte.hu \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).