On Wed, 2012-12-26 at 14:00 -0800, David Rientjes wrote: > I do quite a bit of automated config and boot tests to try out > combinations that others may not have tested when developing their > code; staging branches such as in tip are interesting to try because > they haven't yet reached Linus and it's helpful to catch breakages > before it reaches mainline.
Indeed. It seems quite broken at the moment.
Your config builds fine in the tip of Linus' current tree (with
ARCH=i386 or ARCH=x86 of course). But breaks on tip.git as you describe.
The first commit I hit when attempting to bisect (2bd24259f78) is
*differently* buggered:
CC arch/x86/kernel/ptrace.o
arch/x86/kernel/ptrace.c:1350:17: error: conflicting types for
‘syscall_trace_enter’
In file included from /ssd/git/tip/arch/x86/include/asm/vm86.h:130:0,
from /ssd/git/tip/arch/x86/include/asm/processor.h:10,
from /ssd/git/tip/arch/x86/include/asm/thread_info.h:22,
from include/linux/thread_info.h:56,
from include/linux/preempt.h:9,
from include/linux/spinlock.h:50,
from include/linux/seqlock.h:29,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:56,
from arch/x86/kernel/ptrace.c:8:
/ssd/git/tip/arch/x86/include/asm/ptrace.h:146:13: note: previous declaration
of ‘syscall_trace_enter’ was here
I'll persist, but the build failure you describe looks like it's a
simple failure of the 32-bit build in tip.git, which 'randconfig' was
*designed* to catch... but of course it wasn't doing its job very well
until I fixed it. It's entirely inappropriate to *blame* it on my patch.
--
dwmw2
smime.p7s
Description: S/MIME cryptographic signature
