diff options
| author | Alyssa Ross <hi@alyssa.is> | 2025-09-09 19:23:34 +0200 |
|---|---|---|
| committer | Stig Palmquist <git@stig.io> | 2025-11-15 19:34:53 +0100 |
| commit | b5fa38a5e5e7c7b3f4b0ef71141b890391710e4e (patch) | |
| tree | 603906192d42cef460ba61606cb93b1383cb6cd3 /pkgs/development/python-modules/rangehttpserver | |
| parent | 2e2fd3106581c1688b0625a565b46693b705df0c (diff) | |
perl: unconditionally set _GNU_SOURCE
Perl uses GNU extensions if they are available. Its build system
tries to detect whether the libc is one that recognizes _GNU_SOURCE
with bad heuristics, that don't work for e.g. riscv64 musl. Upstream
is not willing to unconditionally set _GNU_SOURCE like programs
usually do, because of an IMO misguided fear of somebody one day
writing a libc that interprets _GNU_SOURCE to mean something
different, so the only thing we can really do is set it ourselves.
On libcs that don't gate GNU extensions behind _GNU_SOURCE, like BSDs,
this should be a no-op. This should also improve things for cross
where musl builds are currently broken due to perl-cross setting
_GNU_SOURCE for the configure step but not the build step, although I
haven't tested that.
Link: https://github.com/Perl/perl5/issues/16807#issuecomment-544099623
Link: https://github.com/arsv/perl-cross/issues/158
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
