From: Nicola Pero <nicola.pero@meta-innovation.com>
To: gcc-patches@gnu.org
Subject: Remove dependency of all-target-libobjc on maybe-all-target-libiberty
Date: Fri, 27 May 2011 17:42:00 -0000 [thread overview]
Message-ID: <FC2BF322-8AA7-4889-9469-91FD35161FDD@meta-innovation.com> (raw)
This patch removes the (maybe) dependency of libobjc from target libiberty from
the makefiles.
I don't know of any reasons why libobjc would need target libiberty; I also looked around
and couldn't spot anything. Most other target libraries don't depend on libiberty; I'm
not sure why libobjc would need to. I think the dependency is bogus, probably exists
for historical reasons and the fact that nobody reviewed that piece of code for a long
time, and should go away. :-)
It wouldn't matter much, but I saw that some people are keen to remove the target libiberty
completely, and I wouldn't want them to spend time trying to figure out why libobjc needs
it. It doesn't. ;-)
Ok to commit ?
Thanks
Index: Makefile.in
===================================================================
--- Makefile.in (revision 174141)
+++ Makefile.in (working copy)
@@ -43412,7 +43412,6 @@
all-target-libjava: maybe-all-target-boehm-gc
all-target-libjava: maybe-all-target-libffi
configure-target-libobjc: maybe-configure-target-boehm-gc
-all-target-libobjc: maybe-all-target-libiberty
all-target-libobjc: maybe-all-target-boehm-gc
all-target-libstdc++-v3: maybe-all-target-libiberty
configure-target-libstdc++-v3: maybe-configure-target-libgomp
Index: ChangeLog
===================================================================
--- ChangeLog (revision 174141)
+++ ChangeLog (working copy)
@@ -1,3 +1,8 @@
+2011-05-27 Nicola Pero <nicola.pero@meta-innovation.com>
+
+ * Makefile.in (all-target-libobjc): Do not depend on
+ maybe-all-target-libiberty.
+
2011-05-11 Paul Pluzhnikov <ppluzhnikov@google.com>
* MAINTAINERS (Write After Approval): Add myself.
reply other threads:[~2011-05-27 16:10 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=FC2BF322-8AA7-4889-9469-91FD35161FDD@meta-innovation.com \
--to=nicola.pero@meta-innovation.com \
--cc=gcc-patches@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).