Bad use of EXEEXT in man/Makefile.am

[Eli Zaretskii]

If someone re-runs autoconf, then on a platform with nonempty EXEEXT
they will be in trouble, because this snippet from man/Makefile.am:

  # Update the man page for a binary program; set up the variables,
  # make sure the binary is up-to-date and then generate the man page.
  man_rule_bin = echo "Updating man page $@" \
    && $(man_rule_0) \
    && echo cd "$$dir" '&&' $(MAKE) $(AM_MAKEFLAGS) $$program$(EXEEXT) \
    &&     (cd "$$dir"  &&  $(MAKE) $(AM_MAKEFLAGS) $$program$(EXEEXT)) \
    && echo $(HELP2MAN) --name=\""$$name"\" -I "$$h2m" "$$dir/$$program" -o 
'$@'\
    &&      $(HELP2MAN) --name="$$name"     -I "$$h2m" "$$dir/$$program" -o '$@'

will want to build ../tp/makeinfo.exe, which can no longer be done.

I guess a fix would be to change man_rule_0 so that it won't use
EXEEXT with makeinfo.

Btw, this part:

   dir="$(top_builddir)/$(native_tools)/$$dir"

yields ..//tp etc. when native_tools is empty, which is correct, but
ugly.