Reported by irc user (and maybe github user?) @esotericnonsense.
Building bitcoin as c++11 and univalue as c++03/c++14 (depending on compiler version) is pretty scary. It’s surprising that this hasn’t caused any issues yet.
I’m afraid the fix is a big pile of autotools nonsense, but the changes are pretty straightforward:
- Add a new macro to simplify passing args to subconfigures (univalue and secp256k1)
- Pass our modified CXX down to univalue
- If using depends, don’t reset the values passed to subconfigures to their defaults
The good news is that this makes it much easier to tweak subconfigure args in the future.