The reason autoreconf runs autoconf before autoheader is that the former
typically gives better error messages than the latter. autoheader
before automake helps avoid a message from automake about missing
config.h.in.
Yes, I saw that in the autoreconf sources. I think it would be
Ralf Wildenhues wrote:
> It probably is a bug. I for one use bison/yacc very sparingly only and
> lack the experience how to deal with it portably. Which is why it would
> be better if someone else worked on fixing it.
For whatever it's worth, I have always found bison's C++ support to be
sub-p
