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 */ 32530b571Schristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp */ 4b1aac1feSchristos 52530b571Schristos /* The date below is automatically updated every day by a bot. During 62530b571Schristos development, we include the date in the tools' version strings 72530b571Schristos (visible in 'ld -v' etc.) because people build binutils from a 82530b571Schristos variety of sources - git, tarballs, distro sources - and we want 92530b571Schristos something that can easily identify the source they used when they 102530b571Schristos report bugs. The bfd version plus date is usually good enough for 112530b571Schristos that purpose. 122530b571Schristos 132530b571Schristos During development, this date ends up in libbfd and libopcodes 142530b571Schristos sonames because people naturally expect shared libraries with the 152530b571Schristos same soname to have compatible ABIs. We could bump the bfd version 162530b571Schristos on every ABI change, but that's just another thing contributors and 172530b571Schristos maintainers would need to remember. Instead, it's much easier for 182530b571Schristos all if the soname contains the date. This is not perfect but is 192530b571Schristos good enough. 202530b571Schristos 212530b571Schristos In releases, the date is not included in either version strings or 222530b571Schristos 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" 26901e7e84Schristos #define REPORT_BUGS_TO "<https://sourceware.org/bugzilla/>" 27