summaryrefslogtreecommitdiff
path: root/support/sdbinutils/bfd/bfdver.h
diff options
context:
space:
mode:
Diffstat (limited to 'support/sdbinutils/bfd/bfdver.h')
-rw-r--r--support/sdbinutils/bfd/bfdver.h22
1 files changed, 0 insertions, 22 deletions
diff --git a/support/sdbinutils/bfd/bfdver.h b/support/sdbinutils/bfd/bfdver.h
deleted file mode 100644
index dbe30ee..0000000
--- a/support/sdbinutils/bfd/bfdver.h
+++ /dev/null
@@ -1,22 +0,0 @@
-/* The date below is automatically updated every day by a bot. During
- development, we include the date in the tools' version strings
- (visible in 'ld -v' etc.) because people build binutils from a
- variety of sources - git, tarballs, distro sources - and we want
- something that can easily identify the source they used when they
- report bugs. The bfd version plus date is usually good enough for
- that purpose.
-
- During development, this date ends up in libbfd and libopcodes
- sonames because people naturally expect shared libraries with the
- same soname to have compatible ABIs. We could bump the bfd version
- on every ABI change, but that's just another thing contributors and
- maintainers would need to remember. Instead, it's much easier for
- all if the soname contains the date. This is not perfect but is
- good enough.
-
- In releases, the date is not included in either version strings or
- sonames. */
-#define BFD_VERSION_DATE 20180127
-#define BFD_VERSION 230000000
-#define BFD_VERSION_STRING "(sdbinutils derived from GNU Binutils) " "2.30"
-#define REPORT_BUGS_TO "<https://sourceforge.net/p/sdcc/bugs/>"