Buildresult: linus/i386-allnoconfig/i386-gcc4.6 built on Jun 12 2018, 03:29
kisskb
Revisions
|
Branches
|
Compilers
|
Configs
|
Build Results
|
Build Failures
|
Status:
OK
Date/Time:
Jun 12 2018, 03:29
Duration:
0:00:15.183444
Builder:
ka1
Revision:
autofs: remove left-over autofs4 stubs (
a2225d931f75ddd3c39f4d0d195fad99dfd68671)
Target:
linus/i386-allnoconfig/i386-gcc4.6
Branch:
linus
Compiler:
i386-gcc4.6
(i386-linux-gcc (GCC) 4.6.3)
Config:
allnoconfig
(
download
)
Log:
Download original
Possible warnings (2)
kernel/printk/printk.c:183:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized] arch/x86/kernel/e820.c:651:16: warning: 'gapstart' may be used uninitialized in this function [-Wuninitialized]
Full Log
# git rev-parse -q --verify a2225d931f75ddd3c39f4d0d195fad99dfd68671^{commit} a2225d931f75ddd3c39f4d0d195fad99dfd68671 already have revision, skipping fetch # git checkout -q -f -B kisskb a2225d931f75ddd3c39f4d0d195fad99dfd68671 # git clean -qxdf # < git log -1 # commit a2225d931f75ddd3c39f4d0d195fad99dfd68671 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Mon Jun 11 08:22:34 2018 -0700 # # autofs: remove left-over autofs4 stubs # # There's no need to retain the fs/autofs4 directory for backward # compatibility. # # Adding an AUTOFS4_FS fragment to the autofs Kconfig and a module alias # for autofs4 is sufficient for almost all cases. Not keeping fs/autofs4 # remnants will prevent "insmod <path>/autofs4/autofs4.ko" from working # but this shouldn't be used in automation scripts rather than # modprobe(8). # # There were some comments about things to look out for with the module # rename in the fs/autofs4/Kconfig that is removed by this patch, see the # commit patch if you are interested. # # One potential problem with this change is that when the # fs/autofs/Kconfig fragment for AUTOFS4_FS is removed any AUTOFS4_FS # entries will be removed from the kernel config, resulting in no autofs # file system being built if there is no AUTOFS_FS entry also. # # This would have also happened if the fs/autofs4 remnants had remained # and is most likely to be a problem with automated builds. # # Please check your build configurations before the removal which will # occur after the next couple of kernel releases. # # Acked-by: Ian Kent <raven@themaw.net> # [ With edits and commit message from Ian Kent ] # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux-gcc --version # < git log --format=%s --max-count=1 a2225d931f75ddd3c39f4d0d195fad99dfd68671 # < make -s -j 48 ARCH=i386 O=/kisskb/build/linus_i386-allnoconfig_i386 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux- allnoconfig # make -s -j 48 ARCH=i386 O=/kisskb/build/linus_i386-allnoconfig_i386 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux- CONFIG_CC_STACKPROTECTOR_AUTO: -fstack-protector available but compiler is broken: disabling /kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl': /kisskb/src/kernel/printk/printk.c:183:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/arch/x86/kernel/e820.c: In function 'e820__setup_pci_gap': /kisskb/src/arch/x86/kernel/e820.c:651:16: warning: 'gapstart' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/net/Makefile:24: CC cannot link executables. Skipping bpfilter. Completed OK # rm -rf /kisskb/build/linus_i386-allnoconfig_i386 # Build took: 0:00:15.183444
© Michael Ellerman 2006-2018.