Tony Finch 06f534fa69 Avoid spurious compilation failures in liburcu headers ...

When liburcu is not installed from a system package, its headers are
not treated as system headers by the compiler, so BIND's -Werror and
other warning options take effect. The liburcu headers have a lot
of inline functions, some of which do not use all their arguments,
which BIND's build treats as an error.

2023-04-27 12:38:53 +02:00

..

comparekeys

…

testdata

…

testkeys

…

.gitignore

…

acl_test.c

…

db_test.c

…

dbdiff_test.c

…

dbiterator_test.c

…

dbversion_test.c

…

dispatch_test.c

…

dns64_test.c

…

dnstap_test.c

…

dst_test.c

…

geoip_test.c

…

Kdh.+002+18602.key

…

keytable_test.c

…

Krsa.+008+29238.key

…

Makefile.am

…

master_test.c

…

mkraw.pl

…

name_test.c

…

nsec3_test.c

…

nsec3param_test.c

…

private_test.c

…

qp_test.c

…

qpmulti_test.c

…

rbt_test.c

…

rbtdb_test.c

…

rdata_test.c

…

rdataset_test.c

…

rdatasetstats_test.c

…

resolver_test.c

…

rsa_test.c

…

sigs_test.c

…

time_test.c

…

tsig_test.c

…

update_test.c

…

zonemgr_test.c

…

zt_test.c

…