From: Rob Browning <rlb@defaultvalue.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Possibility of a ${srcdir}/info/dir target race?
Date: Wed, 22 Oct 2014 18:55:55 -0500 [thread overview]
Message-ID: <87r3xzirqs.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <jwv7fzrx3un.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Such races are possible, of course, but lots of us use "-j2" or more to
> build Emacs, I expect, so if that's the problem, you probably
> got very unlucky.
So far I'm not sure how the buildd output in question could have been
produced, unless make-info-dir is failing internally. (I suppose that's
possible, if unlikely, since it doesn't check for failures when invoking
cp, etc.)
In the output we have:
(cd . && ./build-aux/make-info-dir ${thisdir}/${tempfile}); \
./build-aux/move-if-change ${tempfile} ./info/dir
Creating /«BUILDDIR»/emacs24-24.4+1/debian/build-nox/info-dir.30059...
[...]
make[4]: Entering directory '/«BUILDDIR»/emacs24-24.4+1/debian/build-nox/doc/misc'
[...]
Created /«BUILDDIR»/emacs24-24.4+1/debian/build-nox/info-dir.30059
At this point, unless the unconditional "cp $basefile $outfile" command
in make-info-dir failed, then info-dir.30059 should exist. But then
immediately afterward we see:
mv: cannot move 'info-dir.30059' to './info/dir': No such file or directory
Which means that either the file never existed, or it was somehow
deleted before move-if-change (assuming that's the source of the mv)
gets to it.
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2014-10-22 23:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 19:13 Possibility of a ${srcdir}/info/dir target race? Rob Browning
2014-10-22 20:11 ` Stefan Monnier
2014-10-22 21:22 ` Glenn Morris
2014-10-22 23:18 ` Rob Browning
2014-10-22 23:55 ` Rob Browning [this message]
2014-10-23 3:41 ` Paul Eggert
2014-10-23 5:32 ` Glenn Morris
2014-10-23 5:49 ` Glenn Morris
2014-10-23 15:20 ` Rob Browning
2014-10-23 5:38 ` Glenn Morris
2014-10-23 6:36 ` Paul Eggert
2014-10-23 15:22 ` Rob Browning
2014-10-23 15:43 ` Rob Browning
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3xzirqs.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).