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: rx: drop unused $arch setting Date: Fri, 4 Nov 2022 07:25:18 +0000 (GMT) [thread overview] Message-ID: <20221104072518.C194A3858439@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b0119424d19afcf80997ad5f3128d7ec68e1fafa commit b0119424d19afcf80997ad5f3128d7ec68e1fafa Author: Mike Frysinger <vapier@gentoo.org> Date: Fri Nov 4 14:23:50 2022 +0700 sim: rx: drop unused $arch setting This is only needed for CGEN ports which RX isn't, so drop it. Diff: --- sim/rx/Makefile.in | 2 -- 1 file changed, 2 deletions(-) diff --git a/sim/rx/Makefile.in b/sim/rx/Makefile.in index 4e1f2acf214..3c4efa30506 100644 --- a/sim/rx/Makefile.in +++ b/sim/rx/Makefile.in @@ -37,5 +37,3 @@ SIM_OBJS = \ err.o ## COMMON_POST_CONFIG_FRAG - -arch = rx
reply other threads:[~2022-11-04 7: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=20221104072518.C194A3858439@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: 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).