From: Gunther Nikl <gnikl@justmail.de>
To: binutils <binutils@sourceware.org>
Subject: [PATCH 1/2]: bfd: remove unused NO_WRITE_HEADER_KLUDGE #define
Date: Tue, 26 May 2020 18:14:40 +0200 [thread overview]
Message-ID: <20200526181440.00007d6b@justmail.de> (raw)
In-Reply-To: <20200526181314.000019b6@justmail.de>
NO_WRITE_HEADER_KLUDGE is defined but nowhere used. It seems that this
define is dead for a very long time. I was unable to find a binutils
version using this define.
2020-05-XX Gunther Nikl <gnikl@justmail.de>
* i386aout.c (NO_WRITE_HEADER_KLUDGE): Delete define.
* libaout.h (NO_WRITE_HEADER_KLUDGE): Do not define.
diff --git a/bfd/i386aout.c b/bfd/i386aout.c
index 694301b5bb..61e0306f8d 100644
--- a/bfd/i386aout.c
+++ b/bfd/i386aout.c
@@ -38,7 +38,6 @@
the tokens. */
#define MY(OP) CONCAT2 (i386_aout_,OP)
#define TARGETNAME "a.out-i386"
-#define NO_WRITE_HEADER_KLUDGE 1
#include "sysdep.h"
#include "bfd.h"
diff --git a/bfd/libaout.h b/bfd/libaout.h
index 61746db243..8e62072741 100644
--- a/bfd/libaout.h
+++ b/bfd/libaout.h
@@ -609,9 +609,6 @@ extern bfd_boolean NAME (aout, bfd_free_cached_info)
#define aout_32_get_section_contents _bfd_generic_get_section_contents
#define aout_64_get_section_contents _bfd_generic_get_section_contents
-#ifndef NO_WRITE_HEADER_KLUDGE
-#define NO_WRITE_HEADER_KLUDGE 0
-#endif
#ifndef aout_32_bfd_is_local_label_name
#define aout_32_bfd_is_local_label_name bfd_generic_is_local_label_name
next prev parent reply other threads:[~2020-05-26 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 16:13 [PATCH 0/2]: bfd: cleanups for the generic a.out support Gunther Nikl
2020-05-26 16:14 ` Gunther Nikl [this message]
2020-05-26 16:16 ` [PATCH 2/2]: bfd: make aoutx.h self-contained Gunther Nikl
2020-05-29 3:07 ` [PATCH 0/2]: bfd: cleanups for the generic a.out support Alan Modra
2020-05-29 19:46 ` Gunther Nikl
2020-06-03 14:26 ` Nick Clifton
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=20200526181440.00007d6b@justmail.de \
--to=gnikl@justmail.de \
--cc=binutils@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).