diff options
| author | Maximilian Bosch <maximilian@mbosch.me> | 2021-08-23 12:12:17 +0200 |
|---|---|---|
| committer | Maximilian Bosch <maximilian@mbosch.me> | 2022-02-27 10:25:34 +0100 |
| commit | 49028fb110ffb19e5326879d7ec6245ebd0315d2 (patch) | |
| tree | bad39ab51e874a9eec8a19859615c71ddc0eeb86 /pkgs/development/python-modules/rangehttpserver | |
| parent | 7bc32b3e5cc623a7b4b0fad900db26258592b9e6 (diff) | |
findutils: fix build w/glibc-2.34
This "-D__nonnull\\(params\\)=" leads to a compilation failure in e.g.
the configure phase:
configure:21131: gcc -c -D__nonnull\(params\)= conftest.c >&5
<command-line>: warning: ISO C99 requires whitespace after the macro name
<command-line>: error: stray '\' in program
<command-line>: error: expected ',' or ';' before '(' token
<command-line>: error: stray '\' in program
According to the commit this isn't even needed on Linux.
I confirmed that this is an (expectable) glibc-2.34 thing by checking
that
* the issue doesn't occur with gcc 10/11 on a recent glibc-2.33 staging.
* the issue DOES occur in a docker container with Fedora rawhide (which
has glibc 2.34 and gcc 11).
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
