1b5bf3908Schristos /* This file is automatically generated. DO NOT EDIT! */ 2*22ebeae4Schristos /* Generated from: NetBSD: mknative-gdb,v 1.17 2024/08/18 03:47:55 rin Exp */ 3b5bf3908Schristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp */ 4b5bf3908Schristos 5b5bf3908Schristos /* The date below is automatically updated every day by a bot. During 6b5bf3908Schristos development, we include the date in the tools' version strings 7b5bf3908Schristos (visible in 'ld -v' etc.) because people build binutils from a 8b5bf3908Schristos variety of sources - git, tarballs, distro sources - and we want 9b5bf3908Schristos something that can easily identify the source they used when they 10b5bf3908Schristos report bugs. The bfd version plus date is usually good enough for 11b5bf3908Schristos that purpose. 12b5bf3908Schristos 13b5bf3908Schristos During development, this date ends up in libbfd and libopcodes 14b5bf3908Schristos sonames because people naturally expect shared libraries with the 15b5bf3908Schristos same soname to have compatible ABIs. We could bump the bfd version 16b5bf3908Schristos on every ABI change, but that's just another thing contributors and 17b5bf3908Schristos maintainers would need to remember. Instead, it's much easier for 18b5bf3908Schristos all if the soname contains the date. This is not perfect but is 19b5bf3908Schristos good enough. 20b5bf3908Schristos 21b5bf3908Schristos In releases, the date is not included in either version strings or 22b5bf3908Schristos sonames. */ 23*22ebeae4Schristos #define BFD_VERSION_DATE 20240707 24*22ebeae4Schristos #define BFD_VERSION 242500000 25*22ebeae4Schristos #define BFD_VERSION_STRING "(GNU Binutils) " "2.42.50" 2615a984a0Schristos #define REPORT_BUGS_TO "<https://sourceware.org/bugzilla/>" 27