The build would fail when /bin/sh links to ksh or csh, we only test dash and bash AFAIK. A patch from upstream. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=48b5ea6782ec7e9ab8f9a28438ef0ededa5fe224
1. Step 1 When /bin/sh -> csh: $ bitbake quilt-native $ bitbake quilt-native -c fetch Illegal variable name. Illegal variable name. [snip] uname: extra operand `2' Try `uname --help' for more information. 2. Step 2 * When /bin/sh -> ksh: If there are only a few tasks running, for example, "bitbake quilt-native", the build would be OK, but it would fail if we run "bitbake world" for a while, there would be a lot of "Broken pipe" errors: $bitbake world Exception: CalledProcessError: Command 'cd /path/to/xx; find . -type d -print | tar -cf - -C /path/to/sysroot-destdir -p --files-from - --no-recursion | tar -xf - -C /path/to/xxx' returned non-zero exit status 2 with output tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors find: `standard output': Broken pipe find: write error
