From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Steve Ellcey <sje@cup.hp.com>,
gcc-patches@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Cc: binutils@sourceware.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: PATCH: import move-if-change from gnulib (was: PATCH: PR binutils/12283: bfd/doc doesn't support parallel build)
Date: Fri, 28 Jan 2011 20:15:00 -0000 [thread overview]
Message-ID: <20110128201452.GM7234@gmx.de> (raw)
In-Reply-To: <201101272357.p0RNvPZ13996@lucas.cup.hp.com>
[ adding gcc-patches ]
* Steve Ellcey wrote on Fri, Jan 28, 2011 at 12:57:25AM CET:
> I tried this patch and I think it works. Before patching I got:
>
> mv: cannot move `chew.13844' to `chew': Text file busy
> make[3]: *** [chew] Error 1
> make[2]: *** [bfdt.texi] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [info-recursive] Error 1
> make: *** [all-bfd] Error 2
>
> After applying the patch and doing some builds, I still got the mv
> error message about 'cannot move' but the make did not fail.
Thank you for confirming this.
> Perhaps we should change move-if-needed to send the stderr of the mv
> -f to /dev/null like we do with cmpprog.
I don't think that it is generally useful to hide the error output:
in case of a full disk or a real write error, the message can provide
valuable help in diagnosing the cause. It can otherwise be very tricky
to analyze parallel build failures.
I have meanwhile added an improved and fixed version of my proposed
patch to the (more complete) gnulib copy of move-if-change. See here:
http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/24860/focus=24865
I hereby propose to just import the gnulib copy into GCC and src,
http://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/move-if-change
and document the change in status as below in patches to src/MAINTAINERS
and GCC www. (The Autoconf copy of move-if-change has been updated from
the gnulib one anyway.)
Any reasons against doing so?
Thanks,
Ralf
ChangeLog:
2011-01-28 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* MAINTAINERS (mkinstalldirs): Comes from Automake.
(move-if-change): Comes from gnulib.
diff --git a/MAINTAINERS b/MAINTAINERS
index a471c90..046c5ea 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -38,7 +38,7 @@ config.guess; config.sub; readline/support/config.{sub,guess}
binutils@sourceware.org
gdb-patches@sourceware.org
-depcomp
+depcomp; mkinstalldirs
Send bug reports and patches to bug-automake@gnu.org.
gdb/; readline/; sim/; GDB's part of include/
@@ -69,12 +69,8 @@ ltconfig; ltmain.sh; ltcf-*.sh
sources or submitted to the master file maintainer and brought
in via a merge.
-mkinstalldirs; move-if-change
- autoconf: http://gnu.org
- Patches to autoconf-patches@gnu.org.
- Changes need to be done in tandem with the official AUTOCONF
- sources or submitted to the master file maintainer and brought
- in via a merge.
+move-if-change
+ Send bug reports and patches to bug-gnulib@gnu.org.
symlink-tree
gcc: http://gcc.gnu.org
Index: codingconventions.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.62
diff -u -r1.62 codingconventions.html
--- codingconventions.html 8 Jan 2011 12:12:42 -0000 1.62
+++ codingconventions.html 28 Jan 2011 20:13:41 -0000
@@ -490,6 +490,11 @@
symlink-tree and ylwrap: These are copied from mainline automake, using
<code>automake --add-missing --copy --force-missing</code>.</li>
+<li>move-if-change: gnulib hosts this now. The latest version can be
+retrieved from
+<a href="http://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/move-if-change">http://git.savannah.gnu.org/cgit/gnulib.git/plain/build-aux/move-if-change</a>.
+</li>
+
<li>Top-level config.rpath: This comes originally from gettext, but
gnulib can be considered upstream. The latest version can be retrieved
from
next prev parent reply other threads:[~2011-01-28 20:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 17:00 PATCH: PR binutils/12283: bfd/doc doesn't support parallel build H.J. Lu
2010-12-02 18:08 ` Ralf Wildenhues
2010-12-02 18:16 ` H.J. Lu
2010-12-02 18:20 ` Ralf Wildenhues
2010-12-02 18:22 ` Ralf Wildenhues
2010-12-02 18:32 ` Ralf Wildenhues
2010-12-02 18:40 ` H.J. Lu
2010-12-02 19:01 ` Ralf Wildenhues
2010-12-19 14:37 ` Ralf Wildenhues
2010-12-19 18:23 ` H.J. Lu
2011-01-27 23:57 ` Steve Ellcey
2011-01-28 20:15 ` Ralf Wildenhues [this message]
2011-01-28 21:12 ` PATCH: import move-if-change from gnulib (was: PATCH: PR binutils/12283: bfd/doc doesn't support parallel build) Steve Ellcey
2011-02-12 15:48 ` Ralf Wildenhues
2011-01-28 23:32 ` PATCH: PR binutils/12283: bfd/doc doesn't support parallel build Steve Ellcey
2011-01-29 9:42 ` Ralf Wildenhues
2011-01-31 18:33 ` Steve Ellcey
2011-02-04 6:34 ` Ralf Wildenhues
2011-02-04 17:51 ` Andreas Schwab
2011-02-16 0:07 ` Steve Ellcey
2011-02-16 5:09 ` Ralf Wildenhues
2011-02-16 18:36 ` Andreas Schwab
2011-02-05 0:25 ` Steve Ellcey
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=20110128201452.GM7234@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=hjl.tools@gmail.com \
--cc=sje@cup.hp.com \
/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).