Buildresult: linus/x86_64-randconfig/x86_64-gcc4.6 built on Aug 10 2016, 08:49

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	Failed
Date/Time:	Aug 10 2016, 08:49
Duration:	0:00:08.672541
Builder:	ka3
Revision:	Revert "printk: create pr_<level> functions" (`a0cba2179ea4c1820fce2ee046b6ed90ecc56196)`
Target:	linus/x86_64-randconfig/x86_64-gcc4.6
Branch:	linus
Compiler:	x86_64-gcc4.6 (x86_64-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 Possible warnings (1) scripts/Makefile.gcc-plugins:17: warning: cannot use CONFIG_KCOV: -fsanitize-coverage=trace-pc is not supported by compiler Full Log # git rev-parse -q --verify a0cba2179ea4c1820fce2ee046b6ed90ecc56196^{commit} a0cba2179ea4c1820fce2ee046b6ed90ecc56196 already have revision, skipping fetch # git checkout -q -f -B kisskb a0cba2179ea4c1820fce2ee046b6ed90ecc56196 # git clean -qxdf # git log -1 commit a0cba2179ea4c1820fce2ee046b6ed90ecc56196 Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Tue Aug 9 10:48:18 2016 -0700 Revert "printk: create pr_<level> functions" This reverts commit 874f9c7da9a4acbc1b9e12ca722579fb50e4d142. Geert Uytterhoeven reports: "This change seems to have an (unintendent?) side-effect. Before, pr_() calls without a trailing newline characters would be printed with a newline character appended, both on the console and in the output of the dmesg command. After this commit, no new line character is appended, and the output of the next pr_() call of the same type may be appended, like in: - Truncating RAM at 0x0000000040000000-0x00000000c0000000 to -0x0000000070000000 - Ignoring RAM at 0x0000000200000000-0x0000000240000000 (!CONFIG_HIGHMEM) + Truncating RAM at 0x0000000040000000-0x00000000c0000000 to -0x0000000070000000Ignoring RAM at 0x0000000200000000-0x0000000240000000 (!CONFIG_HIGHMEM)" Joe Perches says: "No, that is not intentional. The newline handling code inside vprintk_emit is a bit involved and for now I suggest a revert until this has all the same behavior as earlier" Reported-by: Geert Uytterhoeven <geert@linux-m68k.org> Requested-by: Joe Perches <joe@perches.com> Cc: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux-gcc --version # < git log --format=%s --max-count=1 a0cba2179ea4c1820fce2ee046b6ed90ecc56196 # < make -j 10 ARCH=x86_64 O=/home/kisskb/slave/build/linus_x86_64-randconfig_x86_64 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux- randconfig KCONFIG_SEED=0x7EDED58C # Added to kconfig CONFIG_STANDALONE=y # Added to kconfig CONFIG_PREVENT_FIRMWARE_BUILD=y # yes \n \| make -j 10 ARCH=x86_64 O=/home/kisskb/slave/build/linus_x86_64-randconfig_x86_64 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux- oldconfig yes: standard output: Broken pipe yes: write error # make -j 10 ARCH=x86_64 O=/home/kisskb/slave/build/linus_x86_64-randconfig_x86_64 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux- make[1]: Entering directory '/home/kisskb/slave/build/linus_x86_64-randconfig_x86_64' GEN ./Makefile scripts/kconfig/conf --silentoldconfig Kconfig scripts/Makefile.gcc-plugins:17: warning: cannot use CONFIG_KCOV: -fsanitize-coverage=trace-pc is not supported by compiler scripts/Makefile.kasan:19: Cannot use CONFIG_KASAN: -fsanitize=kernel-address is not supported by compiler SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_32_ia32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_64_x32.h SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_64.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_x32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h HOSTCC scripts/basic/bin2c CHK include/config/kernel.release Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler UPD include/config/kernel.release /home/kisskb/slave/src/Makefile:1048: recipe for target 'prepare-compiler-check' failed make[1]: * [prepare-compiler-check] Error 1 make[1]: * Waiting for unfinished jobs.... make[1]: * wait: No child processes. Stop. Makefile:150: recipe for target 'sub-make' failed make: * [sub-make] Error 2 Command 'make -j 10 ARCH=x86_64 O=/home/kisskb/slave/build/linus_x86_64-randconfig_x86_64 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux- ' returned non-zero exit status 2 # rm -rf /home/kisskb/slave/build/linus_x86_64-randconfig_x86_64 # Build took: 0:00:08.672541

© Michael Ellerman 2006-2018.