type, which with bash or whatever, doesn't matter. All they need *your*toolchain in $PATH, why not just to put "$CROSS_COMPILE-mkimage" insteadof $(CONFIG_SHELL) $(MKIMAGE) here? mkuboot.sh just searches $PATH formkimage and run it. Double overkill, no?

> >> The Blackfin toolchain includes mkimage, but we dont want to namespace> >> collide with any of the user's system setup, so we prefix it with our> >> toolchain name.> >> >If that matter, `type -path' is bashizm (BloAted SHell), and "blackbox"> >with "dash" (very good `sh' equivalents) will fail. I would recomend to> >use "which" command (btw, Debian has `sh' version of it), if you> >concerned about size and performance.> >> >Nack + proposition to move from `bash' to `sh'.> > the script already uses "#!/bin/bash" and the patch doesnt change any> of the existing conventions ... so if you want to rewrite the existing> code to be POSIX compliant, then do so so i can add back in support> for $CROSS_COMPILE-mkimage