)]}'
{
  "commit": "d82e33deccc23f7198e20177f6164323201064eb",
  "tree": "979b58357143f48ba3e5bc247dca3e3bbe82eeb9",
  "parents": [
    "38c917d808fdb570ddb1215ccf8233a10484ba91"
  ],
  "author": {
    "name": "Brett Werling",
    "email": "bwerl.dev@gmail.com",
    "time": "Thu Nov 17 08:34:19 2022 -0600"
  },
  "committer": {
    "name": "Alan Modra",
    "email": "amodra@gmail.com",
    "time": "Tue Nov 22 08:19:27 2022 +1030"
  },
  "message": "readelf: use fseeko64 or fseeko if possible\n\nChanges readelf to make use first of fseeko64 and then fseeko,\ndepending on which of those is available. If neither is available,\nreverts to the previous behavior of using fseek.\n\nThis is necessary when building readelf for LLP64 systems, where a\nlong will only be 32 bits wide. If the elf file in question is \u003e\u003d 2 GiB,\nthat is greater than the max long value and therefore fseek will fail\nindicating that the offset is negative. On such systems, making use of\nfseeko64 or fseeko will result in the ability so seek past the 2 GiB\nmax long boundary.\n\nNote that large archive handling in readelf remains to be fixed.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4d22a80971b80be05201a3b5274a0d76fef2de65",
      "old_mode": 33188,
      "old_path": "binutils/config.in",
      "new_id": "91fe00af77742265b3a681252322166b90702780",
      "new_mode": 33188,
      "new_path": "binutils/config.in"
    },
    {
      "type": "modify",
      "old_id": "6176d699e57dae67eda3cf00a188540482850a6e",
      "old_mode": 33261,
      "old_path": "binutils/configure",
      "new_id": "46519a317015bddfa0d9c63bac06a2cded3c45ba",
      "new_mode": 33261,
      "new_path": "binutils/configure"
    },
    {
      "type": "modify",
      "old_id": "6b2cbbcbb1bbe53e9ca39ed88b316d62cf5bd5b4",
      "old_mode": 33188,
      "old_path": "binutils/readelf.c",
      "new_id": "044022ec334ebd88a849256153c7bab637f86676",
      "new_mode": 33188,
      "new_path": "binutils/readelf.c"
    }
  ]
}
