summaryrefslogtreecommitdiffstats
path: root/util/crossgcc/sum
diff options
context:
space:
mode:
authorStefan Reinauer <stefan.reinauer@coreboot.org>2015-07-07 00:26:59 +0200
committerStefan Reinauer <stefan.reinauer@coreboot.org>2015-07-07 17:08:16 +0200
commit8ef928af4ed7dd0a42f40017aa4afb6a86575511 (patch)
treee331db5db7d626075136570ead4dc16b6d7e5977 /util/crossgcc/sum
parente9e6e3d93c67c0e5df1b32fe37b1956624503c97 (diff)
downloadcoreboot-8ef928af4ed7dd0a42f40017aa4afb6a86575511.tar.gz
coreboot-8ef928af4ed7dd0a42f40017aa4afb6a86575511.tar.bz2
coreboot-8ef928af4ed7dd0a42f40017aa4afb6a86575511.zip
xcompile: Fix compiler invocation in testcc
While for GCC targets the compiler is just defined as a single binary, for clang it is defined as a binary and some options, e.g.: clang -target i386-elf -ccc-gcc-name i386-elf-gcc When executing the compiler with "$1", the shell will look for a binary with the above name (instead of just clang) and always fail detection of any CFLAGS. By adding -c we prevent the compiler from failing because it can't link a user space program (when what we're looking for, is whether a specific compiler flag can be used to compile a coreboot object file) Change-Id: I1e9ff32fe40efbe3224c69785f31bc277f21d21b Signed-off-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Reviewed-on: http://review.coreboot.org/10816 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'util/crossgcc/sum')
0 files changed, 0 insertions, 0 deletions