From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: linux-2.4.25 intermittent (parallel) build failure
Date: Mon, 1 Mar 2004 23:36:00 +0000 [thread overview]
Message-ID: <200403012336.00411.andrew@walrond.org> (raw)
The failure seems occur when doing
mv script.h sim710_d.h
in drivers/scsi. It's not actually a failure, but mv asking if it should
overwrite a mode 444 file. On the occasions that it suceeds, the file seems
to have been given 644 permissions.
I'm not entirely sure what is going on here, or why it is an intermittent
failure. But perhaps the mv's should have a -f to prevent the question?
Perhaps mv is at fault. The documentation says
"If a destination file exists but is normally unwritable, standard
input is a terminal, and the `-f' or `--force' option is not given,
`mv' prompts the user for whether to replace the file. (You might own
the file, or have write permission on its directory.) If the response
does not begin with `y' or `Y', the file is skipped."
I'm not sure why mv would think stdin is a terminal, since it's called by
make.
Anyhow, Perhaps someone cleverer than I can work it out. Or tell me why I'm
being stupid :)
Andrew Walrond
reply other threads:[~2004-03-01 23:36 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=200403012336.00411.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®