131580a89Sskrll /* This file is automatically generated. DO NOT EDIT! */ 2*b2c35e17Schristos /* Generated from: NetBSD: mknative-binutils,v 1.16 2024/06/30 16:11:11 christos Exp */ 36f226886Schristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp */ 431580a89Sskrll 56f226886Schristos /* The date below is automatically updated every day by a bot. During 66f226886Schristos development, we include the date in the tools' version strings 76f226886Schristos (visible in 'ld -v' etc.) because people build binutils from a 86f226886Schristos variety of sources - git, tarballs, distro sources - and we want 96f226886Schristos something that can easily identify the source they used when they 106f226886Schristos report bugs. The bfd version plus date is usually good enough for 116f226886Schristos that purpose. 126f226886Schristos 136f226886Schristos During development, this date ends up in libbfd and libopcodes 146f226886Schristos sonames because people naturally expect shared libraries with the 156f226886Schristos same soname to have compatible ABIs. We could bump the bfd version 166f226886Schristos on every ABI change, but that's just another thing contributors and 176f226886Schristos maintainers would need to remember. Instead, it's much easier for 186f226886Schristos all if the soname contains the date. This is not perfect but is 196f226886Schristos good enough. 206f226886Schristos 216f226886Schristos In releases, the date is not included in either version strings or 226f226886Schristos sonames. */ 23*b2c35e17Schristos #define BFD_VERSION_DATE 20240129 24*b2c35e17Schristos #define BFD_VERSION 242000000 25*b2c35e17Schristos #define BFD_VERSION_STRING "(NetBSD Binutils nb1)" " " "2.42" 26321d0b6eSskrll #define REPORT_BUGS_TO "<http://www.NetBSD.org/support/send-pr.html>" 27