• Nils Goroll's avatar
    Bring back close_range() support proper · 1af069bc
    Nils Goroll authored
    As noted in 31baed29, my commit
    0c1aef58 was wrong, and it was even
    worse than we thought:
    
    Despite what the linux man page suggests, the close_range()
    declaration is in unistd.h on Linux like on freebsd.
    
    We do not actually need linux/close_range.h, because it has only
    macro definitions which we do not need.
    
    We now add a specific configure test if close_range() not only exists
    but also works.
    
    Closes #3905
    1af069bc
Name
Last commit
Last update
.circleci Loading commit data...
.github Loading commit data...
bin Loading commit data...
contrib Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
tools Loading commit data...
vmod Loading commit data...
.dir-locals.el Loading commit data...
.editorconfig Loading commit data...
.gitignore Loading commit data...
.lgtm.yml Loading commit data...
.syntastic_c_config Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.Packaging Loading commit data...
README.rst Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish-legacy.m4 Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...
vsc.am Loading commit data...
vtc.am Loading commit data...
wflags.py Loading commit data...