public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Thu, 16 Sep 2021 16:37:19 +0000	[thread overview]
Message-ID: <bug-102353-4-e6woimWeSQ@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 #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:

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

commit r12-3581-gacd7e7b33fd576b336ca0bf5ec51f77b32ba51cc
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Sep 16 18:35:34 2021 +0200

    PowerPC: Fix rs6000-gen-builtins with build != host [PR102353]

    This mimics what the main Makefile.in does: compile the generator
    files under build (with Makefile.in's 'build/%.o' rule for compilation).
    It also adds $(RUN_GEN) to optionally run it with valgrind and
    the $(build_exeext) suffix.

    Before, the .o files were compiled with $(COMPILE), causing link
    error with $(LINKER_FOR_BUILD) for build != host.

    gcc/
            PR target/102353
            * config/rs6000/t-rs6000 (build/rs6000-gen-builtins.o,
build/rbtree.o):
            Added 'build/' to target, use build/%.o rule.
            (build/rs6000-gen-builtins$(build_exeext)): Add 'build/' and
            '$(build_exeext)' to target and 'build/' for the *.o files.
            (rs6000-builtins.c): Update for those changes; run
rs6000-gen-builtins
            with $(RUN_GEN).

  parent reply	other threads:[~2021-09-16 16:37 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
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 [this message]
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-e6woimWeSQ@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: 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).