From: Iain Sandoe <developer@sandoe-acoustics.co.uk>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, Mike Stump <mrs@gcc.gnu.org>
Subject: [Patch Darwin/PR49992 1/2] remove ranlib special-casing from the darwin port.
Date: Fri, 14 Oct 2011 10:13:00 -0000 [thread overview]
Message-ID: <612C0CE1-5848-472C-85CA-6B58C5B36800@sandoe-acoustics.co.uk> (raw)
As per the PR audit trail, there is no reason to retain this special-
casing for Darwin.
(given that current GCC is not build-able using Darwin toolsets of
the vintage that required the case).
Mike has OK'd this off-list - but, since Ralf commented on the
previous version, I'd like to give him the opportunity to comment here.
OK for trunk?
Iain
* configure.ac: Remove ranlib special case for Darwin port.
* gcc/configure.ac: Likewise.
* configure: Regenerate.
* gcc/configure: Regenerate.
Index: configure.ac
===================================================================
--- configure.ac (revision 179962)
+++ configure.ac (working copy)
@@ -2274,10 +2274,6 @@ case "${target}" in
extra_arflags_for_target=" -X32_64"
extra_nmflags_for_target=" -B -X32_64"
;;
- *-*-darwin[[3-9]]*)
- # ranlib before Darwin10 requires the -c flag to look at common
symbols.
- extra_ranlibflags_for_target=" -c"
- ;;
esac
alphaieee_frag=/dev/null
Index: gcc/configure.ac
===================================================================
--- gcc/configure.ac (revision 179962)
+++ gcc/configure.ac (working copy)
@@ -829,17 +829,7 @@ esac
gcc_AC_PROG_LN_S
ACX_PROG_LN($LN_S)
AC_PROG_RANLIB
-case "${host}" in
-*-*-darwin*)
- # By default, the Darwin ranlib will not treat common symbols as
- # definitions when building the archive table of contents. Other
- # ranlibs do that; pass an option to the Darwin ranlib that makes
- # it behave similarly.
- ranlib_flags="-c"
- ;;
-*)
- ranlib_flags=""
-esac
+ranlib_flags=""
AC_SUBST(ranlib_flags)
gcc_AC_PROG_INSTALL
next reply other threads:[~2011-10-14 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 10:13 Iain Sandoe [this message]
2011-10-22 13:47 ` PING * : " Iain Sandoe
2011-10-28 15:52 ` PING 2 " Iain Sandoe
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=612C0CE1-5848-472C-85CA-6B58C5B36800@sandoe-acoustics.co.uk \
--to=developer@sandoe-acoustics.co.uk \
--cc=Ralf.Wildenhues@gmx.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=mrs@gcc.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).