From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Michael Matz <matz@suse.de>
Cc: bonzini@gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Merge OBJS-common,-md,-archive
Date: Fri, 20 May 2011 18:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1105201638220.995@digraph.polyomino.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1105201538070.19219@wotan.suse.de>
That patch left a stray reference to $(OBJS-common) in a comment. I've
applied this patch as obvious to fix this.
Index: ChangeLog
===================================================================
--- ChangeLog (revision 173962)
+++ ChangeLog (working copy)
@@ -1,3 +1,7 @@
+2011-05-20 Joseph Myers <joseph@codesourcery.com>
+
+ * Makefile.in: Update comment referring to $(OBJS-common).
+
2011-05-20 Ian Lance Taylor <iant@google.com>
* godump.c (go_output_typedef): Put enum constants in the macro
Index: Makefile.in
===================================================================
--- Makefile.in (revision 173962)
+++ Makefile.in (working copy)
@@ -3848,7 +3848,7 @@
$(ALL_GTFILES_H) gtype-desc.c gtype-desc.h gcov-iov.h
# In order for parallel make to really start compiling the expensive
-# objects from $(OBJS-common) as early as possible, build all their
+# objects from $(OBJS) as early as possible, build all their
# prerequisites strictly before all objects.
$(ALL_HOST_OBJS) : | $(generated_files)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-05-20 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:51 Link more common objects consistently into host programs Joseph S. Myers
2011-05-20 14:12 ` Paolo Bonzini
2011-05-20 14:35 ` Merge OBJS-common,-md,-archive Michael Matz
2011-05-20 14:41 ` Paolo Bonzini
2011-05-20 18:20 ` Joseph S. Myers [this message]
2011-05-20 15:57 ` Link more common objects consistently into host programs Gabriel Dos Reis
2011-05-20 16:39 ` Rainer Orth
2011-05-20 18:01 ` Tom Tromey
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=Pine.LNX.4.64.1105201638220.995@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
/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).