From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] GNU-ld: ARM: Issues when trying to set target output architecture
Date: Mon, 13 Nov 2023 16:24:45 +0000 (GMT) [thread overview]
Message-ID: <20231113162445.BC6A13858C29@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b0dfd7427be1c022581ea4ff33713e9922294c34
commit b0dfd7427be1c022581ea4ff33713e9922294c34
Author: Nick Clifton <nickc@redhat.com>
Date: Mon Nov 13 16:24:19 2023 +0000
GNU-ld: ARM: Issues when trying to set target output architecture
PR 28910
* lexsup.c (ld_options): Ensure that the --format option is correctly recognised.
Diff:
---
ld/ChangeLog | 6 ++++++
ld/lexsup.c | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/ld/ChangeLog b/ld/ChangeLog
index 316ef47e93b..b9d6c317f97 100644
--- a/ld/ChangeLog
+++ b/ld/ChangeLog
@@ -1,3 +1,9 @@
+2023-11-13 Nick Clifton <nickc@redhat.com>
+
+ PR 28910
+ * lexsup.c (ld_options): Ensure that the --format option is
+ correctly recognised.
+
2023-11-13 Chung-Ju Wu <jasonwucj@gmail.com>
* ld.texi: Fix redundant space typo.
diff --git a/ld/lexsup.c b/ld/lexsup.c
index aa4c76ec281..ce0d7334dd8 100644
--- a/ld/lexsup.c
+++ b/ld/lexsup.c
@@ -108,7 +108,7 @@ static const struct ld_option ld_options[] =
'A', N_("ARCH"), N_("Set architecture") , EXACTLY_TWO_DASHES },
{ {"format", required_argument, NULL, 'b'},
'b', N_("TARGET"), N_("Specify target for following input files"),
- TWO_DASHES },
+ EXACTLY_TWO_DASHES },
{ {"mri-script", required_argument, NULL, 'c'},
'c', N_("FILE"), N_("Read MRI format linker script"), TWO_DASHES },
{ {"dc", no_argument, NULL, 'd'},
reply other threads:[~2023-11-13 16:24 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=20231113162445.BC6A13858C29@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-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).