Build regression omap2plus_defconfig, multi_v7_defconfig builds fine
Tony,
make omap2plus_defconfig ;make zImage on next-20140702
Quoted 15 lines
LD
fs/built-in.oscripts/mod/modpost.c: In function ‘remove_dot’:scripts/mod/modpost.c:1710:10: warning: ignoring return value of ‘strtoul’, declared with attributewarn_unused_result[-Wunused-result]arch/arm/kernel/return_address.c:63:2: warning: #warning "TODO:return_addressshould use unwind tables" [-Wcpp]arch/arm/kernel/return_address.c:63:2: warning: #warning "TODO:return_addressshould use unwind tables" [-Wcpp] In file included fromarch/arm/kernel/perf_event_cpu.c:69:0:arch/arm/kernel/perf_event_v6.c: In function ‘armv6_1136_pmu_init’:arch/arm/kernel/perf_event_v6.c:498:2: error: expected ‘;’ before ‘return’arch/arm/kernel/perf_event_v6.c:499:1: warning: no return statement in function returning non-void [-Wreturn-type]arch/arm/kernel/perf_event_v6.c: In function ‘armv6_1156_pmu_init’:arch/arm/kernel/perf_event_v6.c:505:2: error: expected ‘;’ before ‘return’arch/arm/kernel/perf_event_v6.c:506:1: warning: no return statement in function returning non-void [-Wreturn-type]arch/arm/kernel/perf_event_v6.c: In function ‘armv6_1176_pmu_init’:arch/arm/kernel/perf_event_v6.c:512:2: error: expected ‘;’ before ‘return’arch/arm/kernel/perf_event_v6.c:513:1: warning: no return statement in function returning non-void [-Wreturn-type]
Quoted 8 lines
make[1]: *** [
arch/arm/kernel/perf_event_cpu.o] Error 1
make: *** [arch/arm/kernel] Error 2
make: *** Waiting for unfinished jobs....fs/direct-io.c: In function ‘__blockdev_direct_IO’:fs/direct-io.c:1011:12: warning: ‘to’ may be used uninitialized in this function [-Wuninitialized]fs/direct-io.c:913:16: note: ‘to’ was declared herefs/direct-io.c:920:9: warning: ‘from’ may be used uninitialized in this function [-Wuninitialized]fs/direct-io.c:913:10: note: ‘from’ was declared here
multi_v7_defconfig seems to build fine.
Signature · 6 lines
Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html