summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorEmily <vcs@emily.moe>2024-11-17 12:28:53 +0000
committerEmily <vcs@emily.moe>2024-11-19 15:13:36 +0000
commit0d933223a8b61265c6b3d05d90b2a3c523b58f1c (patch)
tree94243a8d0d320f25ecf629c203012e70e5b1682b /pkgs/development/python-modules/rangehttpserver
parent1634419f4f629111c7b66f370155a26d98c53505 (diff)
gcc14: 14.2.0 -> 14-20241116
The stable release has too many AArch64 issues, but they seem to have been fixed upstream; Arch is shipping a Git snapshot. The next stable release should be out by the time 25.05 is finishing up, so this should be okay as a temporary solution. This is the GCC 14-20241116 snapshot. We use that identifier as our package version, diverging from our usual unstable version convention, because it identifies itself as “gcc (GCC) 14.2.1 20241116” and comes in `gcc-14-20241116.tar.xz`; 20241116 is therefore a useful version identifier to use verbatim, and 14.2.0-unstable-2024-11-16 would potentially be confusing for a version that calls itself 14.2.1. The next stable release from the GCC 14 branch will be 14.3.0, so there should be no ambiguity here. Getting this version is a little complicated; we need the precompiled `flex(1)` output that these Git snapshots don’t include. Thankfully, the source file hasn’t changed since 14.2.0, so we can simply download 14.2.0 too and extract the precompiled file. A little merging finesse is required for the `aarch64-darwin` patch, which we also upgrade.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions