From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Fix another linker command line option that was not being recognised in its long form.
Date: Tue, 14 Nov 2023 11:25:40 +0000 (GMT) [thread overview]
Message-ID: <20231114112540.930433858298@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b2a6584d753a4dc94139e98c6998f570ed1e2341
commit b2a6584d753a4dc94139e98c6998f570ed1e2341
Author: Nick Clifton <nickc@redhat.com>
Date: Tue Nov 14 11:24:58 2023 +0000
Fix another linker command line option that was not being recognised in its long form.
PR 28910
* lexsup.c (ld_options): Ensure that the --mri-script 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 b9d6c317f97..287e2cfef3a 100644
--- a/ld/ChangeLog
+++ b/ld/ChangeLog
@@ -1,3 +1,9 @@
+2023-11-14 Nick Clifton <nickc@redhat.com>
+
+ PR 28910
+ * lexsup.c (ld_options): Ensure that the --mri-script option is
+ correctly recognised.
+
2023-11-13 Nick Clifton <nickc@redhat.com>
PR 28910
diff --git a/ld/lexsup.c b/ld/lexsup.c
index ce0d7334dd8..a7c0eb1d277 100644
--- a/ld/lexsup.c
+++ b/ld/lexsup.c
@@ -110,7 +110,7 @@ static const struct ld_option ld_options[] =
'b', N_("TARGET"), N_("Specify target for following input files"),
EXACTLY_TWO_DASHES },
{ {"mri-script", required_argument, NULL, 'c'},
- 'c', N_("FILE"), N_("Read MRI format linker script"), TWO_DASHES },
+ 'c', N_("FILE"), N_("Read MRI format linker script"), EXACTLY_TWO_DASHES },
{ {"dc", no_argument, NULL, 'd'},
'd', NULL, N_("Force common symbols to be defined"), ONE_DASH },
{ {"dp", no_argument, NULL, 'd'},
reply other threads:[~2023-11-14 11: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=20231114112540.930433858298@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).