There's an ordering problem around the definition of sigset_t: the definition in the kernel-specific header is referred to in the user-specific header data structures, at least for x86. When compiling userspace, the user-specific header provides an alternate version of sigset_t. To get around this problem, place a marker specifically to indicate the point at which the #include_next should be placed in the kernel-specific file. Signed-off-by: David Howells <dhowells@xxxxxxxxxx> --- arch/x86/include/asm/signal.h | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/arch/x86/include/asm/signal.h b/arch/x86/include/asm/signal.h index 598457c..40ef827 100644 --- a/arch/x86/include/asm/signal.h +++ b/arch/x86/include/asm/signal.h @@ -40,6 +40,8 @@ typedef unsigned long sigset_t; #endif /* __KERNEL__ */ #endif /* __ASSEMBLY__ */ +// DISINTEGRATE: INCLUDE UAPI HERE + #define SIGHUP 1 #define SIGINT 2 #define SIGQUIT 3 -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
