Faulty ./binutils/po/Make-in or configure in binutils-2.13.90.0.4

[Erik Christiansen]

Environment:
   debian woody
   GNU Make version 3.79.1
   GNU m4 1.4
   gcc 2.95.4

   ./configure --target=powerpc-linux completes happily, but make
results in the following broken scripting being executed: 

 cd .. \
   && CONFIG_FILES=po/Makefile.in:po/Make-in \
      CONFIG_HEADERS= /bin/sh ./config.status
 creating po/Makefile.in
 make[3]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd/po'
 make[3]: Entering directory `/usr/local/src/binutils-2.13.90.0.4/bfd/po'
 file=./`echo sv | sed 's,.*/,,'`.gmo \
   && rm -f $file && PATH=../src:$PATH no -o $file sv.po
 /bin/sh: no: command not found
 make[3]: *** [sv.gmo] Error 127
 make[3]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd/po'
 make[2]: *** [all-recursive] Error 1
 make[2]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd'
 make[1]: *** [all-recursive-am] Error 2
 make[1]: Leaving directory `/usr/local/src/binutils-2.13.90.0.4/bfd'
 make: *** [all-bfd] Error 2
 
   Looking in ./binutils/po/Make-in, we find:

GMSGFMT = PATH=../src:$$PATH @GMSGFMT@

.po.gmo:
   file=$(srcdir)/`echo $* | sed 's,.*/,,'`.gmo \
        && rm -f $$file && $(GMSGFMT) -o $$file $<

   OK, is the generated scripting broken, or is it really truly setting
PATH prior to executing a heretofore unknown "no" command, that
configure fails to check for?

   Identical outcomes occurred with binutils-2.11.93.0.2,
binutils-2.12.90.0.9, and binutils-2.13.90.0.4.