summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorLuna Nova <git@lunnova.dev>2025-11-14 05:31:07 -0800
committerLuna Nova <git@lunnova.dev>2025-11-14 07:32:04 -0800
commitce37d84094757a3bd7d244144c3edc63de5ce5ee (patch)
tree12d6035122bbf5796df3a2afea5e2e8941c8e67e /pkgs/development/python-modules/rangehttpserver
parent38ab204bb046824462652a482411f669c87bcbfa (diff)
go: revert default PIE changes
Reverts default PIE patch for go. Does not reintroduce usages of removed "pie" hardening flag. I've made a right mess 😿; we have to back go default PIE out late. building with -race was just reported broken, there isn't time to investigate. fixing is a mass rebuild. People are using nixpkgs' go outside of nix derivations to produce executables to copy into containers. buildGoModule currently sets buildmode=exe when CGO_ENABLED=0 but this does nothing to maintain the existing interface for external users. We are fortunate that backing out the go PIE change in this manner does not reintroduce breakage of pkgsMusl.rclone etc that previously occurred when buildmode=pie *wasn't* set. The gcc `--enable-default-pie` approach turns out to not cause problems when mixed with a non-PIE go externally linked build. Historical issues were due to our linker wrapper being less smart about enabling PIE. Default PIE for go should be revisited post branch off. Fixes: #456953 Fixes: #461539
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions