public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Olivier Hainque <hainque@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-5869] Fix path to t-ppc64-fp for ppc*-vxworks7* libgcc tmake_file
Date: Thu,  9 Dec 2021 17:50:58 +0000 (GMT)	[thread overview]
Message-ID: <20211209175058.E5DC13858C3A@sourceware.org> (raw)

https://gcc.gnu.org/g:a2c12cb70892d82506b3044c4c34f5667eb12835

commit r12-5869-ga2c12cb70892d82506b3044c4c34f5667eb12835
Author: Frederic Konrad <konrad@adacore.com>
Date:   Thu Jan 14 09:08:40 2021 +0100

    Fix path to t-ppc64-fp for ppc*-vxworks7* libgcc tmake_file
    
    This fixes a basic mistake in the relative path used to reference
    a rs6000 specific Makefile fragment in the libgcc configuration bits
    for powerpc*-vxworks7.
    
    2021-01-14  Fred Konrad  <konrad@adacore.com>
    
    libgcc/
            * config.host (powerpc*-wrs-vxworks7*): Fix path to
            rs6000/t-ppc64-fp, relative to config/ not libgcc/.

Diff:
---
 libgcc/config.host | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libgcc/config.host b/libgcc/config.host
index d4c035c7188..95a0b2ab4b1 100644
--- a/libgcc/config.host
+++ b/libgcc/config.host
@@ -1238,7 +1238,7 @@ powerpc*-*-linux*)
 	md_unwind_header=rs6000/linux-unwind.h
 	;;
 powerpc*-wrs-vxworks7*)
-        tmake_file="$tmake_file rs6000/t-ppccomm rs6000/t-savresfgpr rs6000/t-crtstuff rs6000/t-linux t-dfprules config/rs6000/t-ppc64-fp t-slibgcc-libgcc"
+        tmake_file="$tmake_file rs6000/t-ppccomm rs6000/t-savresfgpr rs6000/t-crtstuff rs6000/t-linux t-dfprules rs6000/t-ppc64-fp t-slibgcc-libgcc"
         case $ppc_fp_type in
         64)
                 ;;


                 reply	other threads:[~2021-12-09 17:50 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=20211209175058.E5DC13858C3A@sourceware.org \
    --to=hainque@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).