xref: /netbsd-src/external/gpl3/binutils/lib/libbfd/arch/sparc/bfdver.h (revision 801f73adf8029e41ec107911c58034bb925796a2)
131580a89Sskrll /* This file is automatically generated.  DO NOT EDIT! */
2*801f73adSchristos /* Generated from: NetBSD: mknative-binutils,v 1.16 2024/06/30 16:11:11 christos Exp  */
38005419bSchristos /* Generated from: NetBSD: mknative.common,v 1.16 2018/04/15 15:13:37 christos Exp  */
431580a89Sskrll 
58005419bSchristos /* The date below is automatically updated every day by a bot.  During
68005419bSchristos    development, we include the date in the tools' version strings
78005419bSchristos    (visible in 'ld -v' etc.) because people build binutils from a
88005419bSchristos    variety of sources - git, tarballs, distro sources - and we want
98005419bSchristos    something that can easily identify the source they used when they
108005419bSchristos    report bugs.  The bfd version plus date is usually good enough for
118005419bSchristos    that purpose.
128005419bSchristos 
138005419bSchristos    During development, this date ends up in libbfd and libopcodes
148005419bSchristos    sonames because people naturally expect shared libraries with the
158005419bSchristos    same soname to have compatible ABIs.  We could bump the bfd version
168005419bSchristos    on every ABI change, but that's just another thing contributors and
178005419bSchristos    maintainers would need to remember.  Instead, it's much easier for
188005419bSchristos    all if the soname contains the date.  This is not perfect but is
198005419bSchristos    good enough.
208005419bSchristos 
218005419bSchristos    In releases, the date is not included in either version strings or
228005419bSchristos    sonames.  */
23*801f73adSchristos #define BFD_VERSION_DATE 20240129
24*801f73adSchristos #define BFD_VERSION 242000000
25*801f73adSchristos #define BFD_VERSION_STRING  "(NetBSD Binutils nb1)" " " "2.42"
26321d0b6eSskrll #define REPORT_BUGS_TO "<http://www.NetBSD.org/support/send-pr.html>"
27