[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090419081641.GA23906@elte.hu>
Date: Sun, 19 Apr 2009 10:16:41 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Wu Zhangjin <wuzhangjin@...il.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Ralf Baechle <ralf@...ux-mips.org>,
LKML <linux-kernel@...r.kernel.org>, linux-mips@...ux-mips.org,
Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: mips build failure
* Wu Zhangjin <wuzhangjin@...il.com> wrote:
> On Sun, 2009-04-19 at 17:24 +1000, Stephen Rothwell wrote:
> > Hi Ralf,
> >
> > You probably already now about this, but our build (mips ip32_defconfig)
> > of Linus' tree (commit aefe6475720bd5eb8aacbc881488f3aa65618562 "Merge
> > branch 'upstream-linus' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev") gets
> > these errors (we have actually been getting these errors since 2.6.30-rc1):
> >
> > In file included from arch/mips/include/asm/compat.h:7,
> > from include/linux/compat.h:15,
> > from arch/mips/kernel/asm-offsets.c:12:
> > include/linux/seccomp.h: In function 'prctl_get_seccomp':
> > include/linux/seccomp.h:30: error: 'EINVAL' undeclared (first use in this function)
> > include/linux/seccomp.h:30: error: (Each undeclared identifier is reported only once
> > include/linux/seccomp.h:30: error: for each function it appears in.)
> > include/linux/seccomp.h: In function 'prctl_set_seccomp':
> > include/linux/seccomp.h:35: error: 'EINVAL' undeclared (first use in this function)
> >
>
> perhaps you can fix it like this:
>
> include/linux/seccomp.h
>
> 22 #else /* CONFIG_SECCOMP */
> 23
> 24 +#include <asm-generic/errno-base.h>
> 25
> 26 typedef struct { } seccomp_t;
>
> in reality, there is a previous email sent by Ralf for it:
>
> http://lkml.indiana.edu/hypermail/linux/kernel/0904.2/01152.html
Yes, that looks like the right kind of fix.
Ralf, will you push that fix upstream, or should i do it?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists