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: drop common/nrun.o subdir hack
Date: Tue, 10 Jan 2023 06:25:27 +0000 (GMT)	[thread overview]
Message-ID: <20230110062527.959C83858CDB@sourceware.org> (raw)

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

commit 638a9300b519307d9c85f3cd658f35c4d354a80c
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sat Dec 31 15:51:38 2022 -0500

    sim: build: drop common/nrun.o subdir hack
    
    Now that all the subdirs handle their own builds, we can drop this
    common rule as it's unused, and we don't want to use it anymore.

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

diff --git a/sim/Makefile.am b/sim/Makefile.am
index 8a4a160b30c..e47244d7b8d 100644
--- a/sim/Makefile.am
+++ b/sim/Makefile.am
@@ -188,9 +188,6 @@ endif
 ## Helper targets for running make from the top-level when some subdirs still
 ## have Makefiles in subdirs.
 
-%/nrun.o: common/nrun.c | %/libsim.a $(SIM_ALL_RECURSIVE_DEPS)
-	$(MAKE) $(AM_MAKEFLAGS) -C $(@D) $(@F)
-
 all-recursive: $(SIM_ALL_RECURSIVE_DEPS)
 
 install-data-local: installdirs $(SIM_INSTALL_DATA_LOCAL_DEPS)
diff --git a/sim/Makefile.in b/sim/Makefile.in
index dc306157b30..0a2f4a991ee 100644
--- a/sim/Makefile.in
+++ b/sim/Makefile.in
@@ -5485,9 +5485,6 @@ testsuite/common/bits64m63.c: testsuite/common/bits-gen$(EXEEXT) testsuite/commo
 @SIM_ENABLE_ARCH_v850_TRUE@		-n irun.c      -r  v850/irun.c
 @SIM_ENABLE_ARCH_v850_TRUE@	$(AM_V_at)touch $@
 
-%/nrun.o: common/nrun.c | %/libsim.a $(SIM_ALL_RECURSIVE_DEPS)
-	$(MAKE) $(AM_MAKEFLAGS) -C $(@D) $(@F)
-
 all-recursive: $(SIM_ALL_RECURSIVE_DEPS)
 
 install-data-local: installdirs $(SIM_INSTALL_DATA_LOCAL_DEPS)

                 reply	other threads:[~2023-01-10  6:25 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=20230110062527.959C83858CDB@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).