public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mips@linux-mips.org,
	Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: mips build failure
Date: Sun, 19 Apr 2009 15:32:41 +0800	[thread overview]
Message-ID: <1240126361.3423.5.camel@falcon> (raw)
In-Reply-To: <20090419172436.6d0e741a.sfr@canb.auug.org.au>

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

> Bisected down to commit ac44021fccd8f1f2b267b004f23a2e8d7ef05f7b
> "kmemtrace, rcu: don't include unnecessary headers, allow kmemtrace w/
> tracepoints".
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/330240/


  reply	other threads:[~2009-04-19  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  7:24 mips build failure Stephen Rothwell
2009-04-19  7:32 ` Wu Zhangjin [this message]
2009-04-19  7:38   ` Stephen Rothwell
2009-04-19  8:16   ` Ingo Molnar
2009-04-19 11:41     ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1240126361.3423.5.camel@falcon \
    --to=wuzhangjin@gmail.com \
    --cc=eduard.munteanu@linux360.ro \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=ralf@linux-mips.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox