public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] sim: build: stop passing down SIM_PRIMARY_TARGET
Date: Sun,  6 Nov 2022 14:45:55 +0000 (GMT)	[thread overview]
Message-ID: <20221106144555.72406385AC36@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1e5482d5686b77accc3b935a36b40a37fd699319

commit 1e5482d5686b77accc3b935a36b40a37fd699319
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sun Nov 6 21:08:04 2022 +0700

    sim: build: stop passing down SIM_PRIMARY_TARGET
    
    This was needed when the install step was run in subdirs, but now
    that we process that entirely in the top-level, we don't need to
    pass this down, so drop it.

Diff:
---
 sim/Makefile.am | 2 +-
 sim/Makefile.in | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/sim/Makefile.am b/sim/Makefile.am
index fb28f98ece7..b8d592ade4d 100644
--- a/sim/Makefile.am
+++ b/sim/Makefile.am
@@ -27,7 +27,7 @@ srcroot = $(srcdir)/..
 SUBDIRS = @subdirs@ $(SIM_SUBDIRS)
 
 SIM_PRIMARY_TARGET = @SIM_PRIMARY_TARGET@
-AM_MAKEFLAGS = SIM_PRIMARY_TARGET=$(SIM_PRIMARY_TARGET)
+AM_MAKEFLAGS =
 
 ## We don't set some of these vars here, but we need to define them so they may
 ## be used consistently in local.mk files we include below.
diff --git a/sim/Makefile.in b/sim/Makefile.in
index 9df04fed45a..746527dc7b0 100644
--- a/sim/Makefile.in
+++ b/sim/Makefile.in
@@ -1164,7 +1164,7 @@ GNULIB_PARENT_DIR = ..
 srccom = $(srcdir)/common
 srcroot = $(srcdir)/..
 SUBDIRS = @subdirs@ $(SIM_SUBDIRS)
-AM_MAKEFLAGS = SIM_PRIMARY_TARGET=$(SIM_PRIMARY_TARGET)
+AM_MAKEFLAGS = 
 pkginclude_HEADERS = $(am__append_1)
 noinst_LIBRARIES = $(SIM_COMMON_LIB) $(am__append_3)
 CLEANFILES = common/version.c common/version.c-stamp \

                 reply	other threads:[~2022-11-06 14:45 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=20221106144555.72406385AC36@sourceware.org \
    --to=vapier@sourceware.org \
    --cc=gdb-cvs@sourceware.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).