1867d70fcSchristos /* This file is automatically generated. DO NOT EDIT! */ 2*c42dbd0eSchristos /* Generated from: NetBSD: mknative-binutils,v 1.14 2022/12/24 20:17:46 christos Exp */ 3867d70fcSchristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp */ 4867d70fcSchristos 5867d70fcSchristos /* The date below is automatically updated every day by a bot. During 6867d70fcSchristos development, we include the date in the tools' version strings 7867d70fcSchristos (visible in 'ld -v' etc.) because people build binutils from a 8867d70fcSchristos variety of sources - git, tarballs, distro sources - and we want 9867d70fcSchristos something that can easily identify the source they used when they 10867d70fcSchristos report bugs. The bfd version plus date is usually good enough for 11867d70fcSchristos that purpose. 12867d70fcSchristos 13867d70fcSchristos During development, this date ends up in libbfd and libopcodes 14867d70fcSchristos sonames because people naturally expect shared libraries with the 15867d70fcSchristos same soname to have compatible ABIs. We could bump the bfd version 16867d70fcSchristos on every ABI change, but that's just another thing contributors and 17867d70fcSchristos maintainers would need to remember. Instead, it's much easier for 18867d70fcSchristos all if the soname contains the date. This is not perfect but is 19867d70fcSchristos good enough. 20867d70fcSchristos 21867d70fcSchristos In releases, the date is not included in either version strings or 22867d70fcSchristos sonames. */ 23*c42dbd0eSchristos #define BFD_VERSION_DATE 20220805 24*c42dbd0eSchristos #define BFD_VERSION 239000000 25*c42dbd0eSchristos #define BFD_VERSION_STRING "(NetBSD Binutils nb1)" " " "2.39" 26867d70fcSchristos #define REPORT_BUGS_TO "<http://www.NetBSD.org/support/send-pr.html>" 27