public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102353] powerpc64le-linux-gnu build failure when build != host Date: Wed, 15 Sep 2021 19:49:42 +0000 [thread overview] Message-ID: <bug-102353-4-iqv5JcEhh9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102353-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102353 --- Comment #3 from Bill Schmidt <wschmidt at gcc dot gnu.org> --- Hi Sandra, Does the following work for your cross? diff --git a/gcc/config/rs6000/t-rs6000 b/gcc/config/rs6000/t-rs6000 index 92766d8ea25..738d4cf9493 100644 --- a/gcc/config/rs6000/t-rs6000 +++ b/gcc/config/rs6000/t-rs6000 @@ -53,8 +53,7 @@ rbtree.o: $(srcdir)/config/rs6000/rbtree.c $(POSTCOMPILE) rs6000-gen-builtins: rs6000-gen-builtins.o rbtree.o - $(LINKER_FOR_BUILD) $(BUILD_LINKERFLAGS) $(BUILD_LDFLAGS) -o $@ \ - $(filter-out $(BUILD_LIBDEPS), $^) $(BUILD_LIBS) + $(LINKER) $(ALL_LINKERFLAGS) $(LDFLAGS) $< rbtree.o -o $@ # TODO: Whenever GNU make 4.3 is the minimum required, we should use # grouped targets on this: Thanks! Bill
next prev parent reply other threads:[~2021-09-15 19:49 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-15 17:34 [Bug target/102353] New: " sandra at gcc dot gnu.org 2021-09-15 17:36 ` [Bug target/102353] " sandra at gcc dot gnu.org 2021-09-15 17:38 ` wschmidt at gcc dot gnu.org 2021-09-15 19:49 ` wschmidt at gcc dot gnu.org [this message] 2021-09-15 23:36 ` sandra at gcc dot gnu.org 2021-09-16 9:21 ` burnus at gcc dot gnu.org 2021-09-16 12:50 ` wschmidt at gcc dot gnu.org 2021-09-16 16:37 ` cvs-commit at gcc dot gnu.org 2021-09-16 16:53 ` burnus at gcc dot gnu.org
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=bug-102353-4-iqv5JcEhh9@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).