constants from ldns for a different purpose, that ldns doesn't really
want to expose on non-EdXXX builds.
Bodge it in ldns instead by supporting the same USE_EDxxx cpp macros
that opendnssec uses. Looks to me like ldns are trying to replace them
with something harder to mess about with.
Hopefully the various parts of nlnetlabs responsible for these two
pieces of software will talk to each other and figure something out.
Hopefully this should fix ed25519 with opendnssec as found by an
anonymous reporter on ports@.
opendnssec assumes that all ldns >=1.7 have Ed25519/Ed448 but this isn't
correct. In ldns >= 1.8 the constants related to Ed25519/Ed448 are _not_
available unless those features are available, so builds trying to use
them will fail (previously this was a runtime failure).
opendnssec's autoconf script sets USE_ED25519/USE_ED448 (hardcoded to 1)
but doesn't actually use them in code. Change the code to use them, and
hardcode to 0 for now. Should check LDNS_BUILD_CONFIG_USE_ED25519 and
LDNS_BUILD_CONFIG_USE_ED448 on 1.8+.
Feedback and ok sthen@
pkg/DESCR:
OpenDNSSEC was created as an open-source turn-key solution for DNSSEC.
It secures zone data just before it is published in an authoritative
name server.
