Thanks for the bug report. That's due to an old Autoconf bug. It would have been fixed in Bison 2.5 if we had used the latest Autoconf version to generate Bison.
The next time we release Bison, we should try to use the latest autotools to build it, to avoid similar issues in the future.
