Comment 3 for bug 1496105

I ran into this while working on a release. It appears to be a problem with Bison 3. Here are a few related references:
https://github.com/openwrt/packages/issues/2664
http://stackoverflow.com/questions/33562051/conflicting-types-for-libintl-gettextparse
https://sourceware.org/ml/binutils/2014-12/msg00114.html

One solution is to remove the --with-included-gettext option from the distcheck configure line (easiest, unless there's a reason its there). Another is to break some of the files up and select which to use depending on which version of Bison is used.

I've confirmed that getting rid of the option solves the problem. I'm not sure where the option comes from though, or if there's a reason it's there.