summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorBernardo Meurer <bernardo@meurer.org>2021-07-10 13:17:52 -0700
committerBernardo Meurer <bernardo@meurer.org>2021-07-10 13:17:52 -0700
commit31bb7be11ad36dfec724529be69ebde416e5ac0a (patch)
tree728aa08e7e80caa59050eb99e1d161f15f24f7a3 /pkgs/development/python-modules/rangehttpserver
parentdafb3dfc483a1e12017ac9ddf88907d009b3edec (diff)
linuxManualConfig: don't mangle `--build-id`
In order to have our linux builds be reproducible we patch the `Makefile` to use `--build-id=none` as opposed to the default `--build-id=sha1`. The way we've been doing this, however, caused the flag to be mangled, and being set to `--build-id=none=sha1`. While bfd seems to parse this normally, lld will loudly complain that the flag does not exist: ``` linux> LD .tmp_vmlinux.kallsyms1 linux> ld.lld: error: unknown --build-id style: none=sha1 ``` With this change the flag is now correctly set to `--build-id=none`.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions