On Mon, 29 Jun 2015, Karl Palsson wrote:
> No problem. I totally agree that they _should_ I was just curious whether
> it was really c-ares's job to be _enforcing_ that. It feels a little out of
> scope, and I haven't come across any other projects doing so. It's also
> handled by special m4 macros shipped with c-ares, not by any core autotools
> macros, which is why I brought it up.
We can probably safely change that error to become a warning instead. I'd be
fine with that.
-- / daniel.haxx.seReceived on 2015-06-29