1b1aac1feSchristos /* 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 */ 38d9c9161Schristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp */ 4b1aac1feSchristos 58d9c9161Schristos /* The date below is automatically updated every day by a bot. During 68d9c9161Schristos development, we include the date in the tools' version strings 78d9c9161Schristos (visible in 'ld -v' etc.) because people build binutils from a 88d9c9161Schristos variety of sources - git, tarballs, distro sources - and we want 98d9c9161Schristos something that can easily identify the source they used when they 108d9c9161Schristos report bugs. The bfd version plus date is usually good enough for 118d9c9161Schristos that purpose. 128d9c9161Schristos 138d9c9161Schristos During development, this date ends up in libbfd and libopcodes 148d9c9161Schristos sonames because people naturally expect shared libraries with the 158d9c9161Schristos same soname to have compatible ABIs. We could bump the bfd version 168d9c9161Schristos on every ABI change, but that's just another thing contributors and 178d9c9161Schristos maintainers would need to remember. Instead, it's much easier for 188d9c9161Schristos all if the soname contains the date. This is not perfect but is 198d9c9161Schristos good enough. 208d9c9161Schristos 218d9c9161Schristos In releases, the date is not included in either version strings or 228d9c9161Schristos 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" 26865c57e0Schristos #define REPORT_BUGS_TO "<https://sourceware.org/bugzilla/>" 27