bfd + chew + execute

[NightStrike]

For gcc on windows, gcc won't set the execute bit if the file
extension is not .exe.  bfd does some things while building where it
creates a program called chew... but it does this: gcc -o chew.&&;
../../move-if-change chew.$$ chew.exe

So under certain cross compiler conditions, chew is left in a
non-executable state, whereas gcc -o chew.exe works fine.  Is it
really necessary to mess with the file extension here?  Can we do
something like this?

-        $(CC_FOR_BUILD) -o chew.$$$$ $(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD) \
+        $(CC_FOR_BUILD) -o chew$$$$$(EXEEXT_FOR_BUILD)
$(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD) \

and:

-        $(SHELL) $(srcdir)/../../move-if-change chew.$$$$ $(MKDOC)
+        $(SHELL) $(srcdir)/../../move-if-change
chew$$$$$(EXEEXT_FOR_BUILD) $(MKDOC)


?