Buildresult: linus/sh-randconfig/sh4-gcc4.6 built on Nov 3 2017, 18:00
kisskb
Revisions
|
Branches
|
Compilers
|
Configs
|
Build Results
|
Build Failures
|
Status:
Failed
Date/Time:
Nov 3 2017, 18:00
Duration:
0:00:05.157456
Builder:
ka1
Revision:
Kbuild: don't pass "-C" to preprocessor when processing linker scripts (
5cb0512c02ecd7e6214e912e4c150f4219ac78e0)
Target:
linus/sh-randconfig/sh4-gcc4.6
Branch:
linus
Compiler:
sh4-gcc4.6
(sh4-linux-gcc (GCC) 4.6.3)
Config:
randconfig
(
download
)
Log:
Download original
Possible errors
make[1]: *** [prepare-compiler-check] Error 1 make: *** [sub-make] Error 2
No warnings found in log.
Full Log
# git rev-parse -q --verify 5cb0512c02ecd7e6214e912e4c150f4219ac78e0^{commit} 5cb0512c02ecd7e6214e912e4c150f4219ac78e0 already have revision, skipping fetch # git checkout -q -f -B kisskb 5cb0512c02ecd7e6214e912e4c150f4219ac78e0 # git clean -qxdf # git log -1 commit 5cb0512c02ecd7e6214e912e4c150f4219ac78e0 Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Thu Nov 2 14:10:37 2017 -0700 Kbuild: don't pass "-C" to preprocessor when processing linker scripts For some odd historical reason, we preprocessed the linker scripts with "-C", which keeps comments around. That makes no sense, since the comments are not meaningful for the build anyway. And it actually breaks things, since linker scripts can't have C++ style "//" comments in them, so keeping comments after preprocessing now limits us in odd and surprising ways in our header files for no good reason. The -C option goes back to pre-git and pre-bitkeeper times, but seems to have been historically used (along with "-traditional") for some odd-ball architectures (ia64, MIPS and SH). It probably didn't matter back then either, but might possibly have been used to minimize the difference between the original file and the pre-processed result. The reason for this may be lost in time, but let's not perpetuate it only because we can't remember why we did this crazy thing. This was triggered by the recent addition of SPDX lines to the source tree, where people apparently were confused about why header files couldn't use the C++ comment format. Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Greg KH <gregkh@linuxfoundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/gcc-4.6.3-nolibc/sh4-linux/bin/sh4-linux-gcc --version # < git log --format=%s --max-count=1 5cb0512c02ecd7e6214e912e4c150f4219ac78e0 # < make -j 48 ARCH=sh O=/home/kisskb/slave/build/linus_sh-randconfig_sh4 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/sh4-linux/bin/sh4-linux- randconfig KCONFIG_SEED=0x7CFDB407 # Added to kconfig CONFIG_STANDALONE=y # yes \n | make -j 48 ARCH=sh O=/home/kisskb/slave/build/linus_sh-randconfig_sh4 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/sh4-linux/bin/sh4-linux- oldconfig yes: standard output: Broken pipe yes: write error # make -j 48 ARCH=sh O=/home/kisskb/slave/build/linus_sh-randconfig_sh4 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/sh4-linux/bin/sh4-linux- make[1]: Entering directory '/home/kisskb/slave/build/linus_sh-randconfig_sh4' GEN ./Makefile scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler /home/kisskb/slave/src/Makefile:1090: recipe for target 'prepare-compiler-check' failed make[1]: *** [prepare-compiler-check] Error 1 make[1]: *** Waiting for unfinished jobs.... UPD include/config/kernel.release make[1]: *** wait: No child processes. Stop. Makefile:146: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 Command 'make -j 48 ARCH=sh O=/home/kisskb/slave/build/linus_sh-randconfig_sh4 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/sh4-linux/bin/sh4-linux- ' returned non-zero exit status 2 # rm -rf /home/kisskb/slave/build/linus_sh-randconfig_sh4 # Build took: 0:00:05.157456
© Michael Ellerman 2006-2018.