public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/meissner/heads/work048)] Do not pass -rpath to linker with advance toolchain for 64 bit builds
Date: Thu, 15 Apr 2021 17:33:04 +0000 (GMT)	[thread overview]
Message-ID: <20210415173304.F3FCB3851C1C@sourceware.org> (raw)

https://gcc.gnu.org/g:0105079f182ea12d8217ac498ec1408d8be786a5

commit 0105079f182ea12d8217ac498ec1408d8be786a5
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Apr 15 13:32:17 2021 -0400

    Do not pass -rpath to linker with advance toolchain for 64 bit builds
    
    (#ltc-toolchain on March 3/8).  Fixed to keep the -rpath option for
    32-bit.
    
    gcc/
    2021-04-15  Michael Meissner  <meissner@linux.ibm.com>
    
            * config.gcc (powerpc*-*-*, rs6000-*-*): Do not set
            LINK_OS_EXTRA_SPEC664 for the Advance Toolchain.  Continue to set
            LINK_OS_EXTRA_SPEC32.

Diff:
---
 gcc/config.gcc | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/gcc/config.gcc b/gcc/config.gcc
index 357b0bed067..f9c9f31d875 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -5102,11 +5102,6 @@ case "${target}" in
 			      "\"%(link_os_new_dtags)" \
 			      "-rpath $prefix/lib -rpath $at/lib\""
 			 echo
-			 echo "#undef  LINK_OS_EXTRA_SPEC64"
-			 echo "#define LINK_OS_EXTRA_SPEC64" \
-			      "\"%(link_os_new_dtags)" \
-			      "-rpath $prefix/lib64 -rpath $at/lib64\""
-			 echo
 			 echo "#undef  LINK_OS_NEW_DTAGS_SPEC"
 			 echo "#define LINK_OS_NEW_DTAGS_SPEC" \
 			      "\"--enable-new-dtags\""


                 reply	other threads:[~2021-04-15 17:33 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=20210415173304.F3FCB3851C1C@sourceware.org \
    --to=meissner@gcc.gnu.org \
    --cc=gcc-cvs@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).