Re: linux-next: Tree for Mar 31 (build failures and culprits)

[Guenter Roeck]

On Wed, Apr 01, 2015 at 12:02:21AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20150330:
> 
> The arm64 tree gained a conflict against the arm-soc tree.
> 
> The idle tree gained a build failure so I used the version from
> next-20150327.
> 
> The tip tree gained conflicts against the pm tree.
> 
> The akpm tree gained a conflict against the mips tree.
> 
> Non-merge commits (relative to Linus' tree): 7277
>  6623 files changed, 304342 insertions(+), 138111 deletions(-)
> 
> ----------------------------------------------------------------------------
> 

Build results:
	total: 121 pass: 94 fail: 27
Failed builds:
	alpha:allmodconfig
	arm:rpc_defconfig
	arm64:defconfig
	cris:defconfig
	cris:etrax-100lx_defconfig
	cris:allnoconfig
	frv:defconfig
	i386:allyesconfig
	i386:allmodconfig
	ia64:defconfig
	m32r:defconfig
	m68k:defconfig
	m68k:allmodconfig
	m68k:sun3_defconfig
	m68k:m5272c3_defconfig
	m68k:m5307c3_defconfig
	m68k:m5249evb_defconfig
	m68k:m5407c3_defconfig
	m68k:m5475evb_defconfig
	mips:allmodconfig
	parisc:defconfig
	parisc:generic-32bit_defconfig
	parisc:a500_defconfig
	parisc:generic-64bit_defconfig
	x86_64:allyesconfig
	xtensa:defconfig
	xtensa:allmodconfig

---
alpha:allmodconfig
mips:allmodconfig

samples/kdbus/kdbus-workers.c: In function âprime_newâ:
samples/kdbus/kdbus-workers.c:930:18: error: â__NR_memfd_createâ undeclared
(first use in this function)
  p->fd = syscall(__NR_memfd_create, "prime-area", MFD_CLOEXEC);

Looks like the kdbus example never worked for the affected architectures.
I don't build allmodconfig for all architectures, so other architectures
may be affected as well.

---
arm64:defconfig

drivers/built-in.o: In function `tegra124_132_clock_init_post':
drivers/clk/tegra/clk-tegra124.c:1496: undefined reference to `tegra_emc_init'

Introduced by commit 32477681f48a ("Merge remote-tracking branch
'arm64/for-next/core'"). Maybe some conflict resolution problem ?
CONFIG_ARCH_TEGRA_132_SOC only builds clk-tegra124.o, but clk-tegra124.o
needs clk-emc.o for tegra_emc_init. clk-emc.c was introduced with commit
4ec9e9975d8c ("clk: tegra: Add EMC clock driver"), but it only adds
clk-emc.o to the CONFIG_ARCH_TEGRA_124_SOC build, not to
CONFIG_ARCH_TEGRA_132_SOC.

On a side note, tegra_emc_init is declared twice, once as static variable
and once as global variable, in different files.

---
cris:defconfig
cris:etrax-100lx_defconfig
cris:allnoconfig
frv:defconfig
ia64:defconfig
m32r:defconfig
m68k (all builds)
parisc (all builds)
arm:rpc_defconfig

In file included from kernel/time/hrtimer.c:57:0:
kernel/time/tick-internal.h: In function 'tick_set_periodic_handler':
kernel/time/tick-internal.h:114:5: error: dereferencing pointer to incomplete type
kernel/time/tick-internal.h:114:23: error: 'tick_handle_periodic' undeclared

tick_handle_periodic is declared inside CONFIG_GENERIC_CLOCKEVENTS but used
outside.

Introduced by commit 01b9fdf7e540 ("tick: Move core only declarations and
functions to core") according to bisect. There may be other problems obscuring
the bisect results, though, since the build failure pattern changes during
bisect.

---
i386:allyesconfig
i386:allmodconfig

drivers/usb/musb/musb_dsps.c: In function 'dsps_read_fifo32':
drivers/usb/musb/musb_dsps.c:624:3: error: implicit declaration of function 'readsl'

Introduced by commit 3e457371f436 ("usb: musb: Fix fifo reads for dm816x with
musb_dsps").

---
x86_64:allyesconfig

drivers/built-in.o: In function `sl811_cs_probe':
sl811_cs.c:(.text+0x1d432f6): undefined reference to `sl811h_driver'

Introduced by commit 1dc6120ef7f0 ("usb: host/sl811-hcd: fix sparse warning"),
a botched cleanup attempt.

---
xtensa

Lots of 'dangerous relocation: l32r: literal placed after use' all over the
place, causing all xtensa builds to fail.

Introduced by commit 779c88c94c34 ("ARM: 8321/1: asm-generic: introduce
.text.fixup input section").
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/