1ac8695a9Schristos /* 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 */ 320cd48c9Schristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp */ 4ac8695a9Schristos 520cd48c9Schristos /* The date below is automatically updated every day by a bot. During 620cd48c9Schristos development, we include the date in the tools' version strings 720cd48c9Schristos (visible in 'ld -v' etc.) because people build binutils from a 820cd48c9Schristos variety of sources - git, tarballs, distro sources - and we want 920cd48c9Schristos something that can easily identify the source they used when they 1020cd48c9Schristos report bugs. The bfd version plus date is usually good enough for 1120cd48c9Schristos that purpose. 1220cd48c9Schristos 1320cd48c9Schristos During development, this date ends up in libbfd and libopcodes 1420cd48c9Schristos sonames because people naturally expect shared libraries with the 1520cd48c9Schristos same soname to have compatible ABIs. We could bump the bfd version 1620cd48c9Schristos on every ABI change, but that's just another thing contributors and 1720cd48c9Schristos maintainers would need to remember. Instead, it's much easier for 1820cd48c9Schristos all if the soname contains the date. This is not perfect but is 1920cd48c9Schristos good enough. 2020cd48c9Schristos 2120cd48c9Schristos In releases, the date is not included in either version strings or 2220cd48c9Schristos 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" 268dbf56feSchristos #define REPORT_BUGS_TO "<https://sourceware.org/bugzilla/>" 27