File: version.h

package info (click to toggle)
binutils 2.33.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 327,132 kB
  • sloc: ansic: 1,178,970; asm: 658,987; cpp: 130,439; exp: 69,405; makefile: 56,638; sh: 22,614; yacc: 14,467; lisp: 14,125; perl: 2,111; ada: 1,681; lex: 1,649; pascal: 1,446; cs: 879; sed: 195; python: 154; xml: 95; awk: 25
file content (22 lines) | stat: -rw-r--r-- 1,125 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
/* The date below is automatically updated every day by a bot.  During
   development, we include the date in the tools' version strings
   (visible in 'ld -v' etc.) because people build binutils from a
   variety of sources - git, tarballs, distro sources - and we want
   something that can easily identify the source they used when they
   report bugs.  The bfd version plus date is usually good enough for
   that purpose.

   During development, this date ends up in libbfd and libopcodes
   sonames because people naturally expect shared libraries with the
   same soname to have compatible ABIs.  We could bump the bfd version
   on every ABI change, but that's just another thing contributors and
   maintainers would need to remember.  Instead, it's much easier for
   all if the soname contains the date.  This is not perfect but is
   good enough.

   In releases, the date is not included in either version strings or
   sonames.  */
#define BFD_VERSION_DATE 20191020
#define BFD_VERSION @bfd_version@
#define BFD_VERSION_STRING  @bfd_version_package@ @bfd_version_string@
#define REPORT_BUGS_TO @report_bugs_to@