11138a3c3Schristos /* 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 */ 35a254e06Schristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp */ 41138a3c3Schristos 55a254e06Schristos /* The date below is automatically updated every day by a bot. During 65a254e06Schristos development, we include the date in the tools' version strings 75a254e06Schristos (visible in 'ld -v' etc.) because people build binutils from a 85a254e06Schristos variety of sources - git, tarballs, distro sources - and we want 95a254e06Schristos something that can easily identify the source they used when they 105a254e06Schristos report bugs. The bfd version plus date is usually good enough for 115a254e06Schristos that purpose. 125a254e06Schristos 135a254e06Schristos During development, this date ends up in libbfd and libopcodes 145a254e06Schristos sonames because people naturally expect shared libraries with the 155a254e06Schristos same soname to have compatible ABIs. We could bump the bfd version 165a254e06Schristos on every ABI change, but that's just another thing contributors and 175a254e06Schristos maintainers would need to remember. Instead, it's much easier for 185a254e06Schristos all if the soname contains the date. This is not perfect but is 195a254e06Schristos good enough. 205a254e06Schristos 215a254e06Schristos In releases, the date is not included in either version strings or 225a254e06Schristos 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" 26ae87de88Schristos #define REPORT_BUGS_TO "<https://sourceware.org/bugzilla/>" 27