The below commit has already been merged and does not resolve the issue. My /bin/sh is also a symlink to bash.

It appears to be 2 things:

1) I don't have the following definitions anywhere

ARCH-BOOTBLOCK-y := i386
ARCH-ROMSTAGE-y := i386
ARCH-RAMSTAGE-y := i386

this is what causes the command not found problems.

2) target build/cbfs/fallback/bootblock.bin is missing. It looks the same in the older codebase Makefile.inc and perhaps is a side-affect of the bootblock class?

On 05/11/2014 01:10 AM, Furquan Shaikh wrote:

This CL has been submitted which should fix the issue:

http://review.coreboot.org/#/c/5701/

On Saturday, May 10, 2014 3:02:44 AM, Sean McNeil <seanmcneil3@gmail.com> wrote:

Up until recently, compiling coreboot with the options

CONFIG_COMPILER_GCC=y
CONFIG_ANY_TOOLCHAIN=y

on a 64-bit linux system worked just fine. Over the last few days I now get the errors:

make
Warning: no suitable GCC for armv7.
Warning: no suitable GCC for aarch64.
/bin/sh: -print-libgcc-file-name: command not found
/bin/sh: -print-libgcc-file-name: command not found
/bin/sh: -print-libgcc-file-name: command not found
/bin/sh: -print-libgcc-file-name: command not found
/bin/sh: -print-libgcc-file-name: command not found
/bin/sh: -print-libgcc-file-name: command not found
#
# configuration written to .config
#
make: *** No rule to make target `build/cbfs/fallback/bootblock.bin', needed by `build/coreboot.pre1'. Stop.

--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org /mailman/listinfo /coreboot