kernel/seccomp.c:55:23: error: 'NR_syscalls' undeclared

Leann Ogasawara leann.ogasawara at canonical.com
Wed Nov 16 19:12:19 UTC 2011


On Wed, 2011-11-16 at 10:52 -0800, Kees Cook wrote:
> Hi,
> 
> Oh, er, I thought Tim was doing the seccomp rebase from what I had in
> https://github.com/kees/linux/commits/ubuntu-precise which (I think)
> fixed the NR_syscalls problem.

Hrm, indeed this is what I thought he'd done as well and pushed the end
result to our official ubuntu-precise repo.  But looking at your tree on
github and comparing that to what we have in our repo, we're definitely
missing some patches.

I'll pull in the extra patches you have in your repo and re-build.  I'll
let you know my results.

Thanks,
Leann

> On Wed, Nov 16, 2011 at 10:43 AM, Leann Ogasawara
> <leann.ogasawara at canonical.com> wrote:
> > Hi Kees and Will,
> >
> > I recently rebased the ubuntu-precise git tree to upstream v3.2-rc2.
> > Unfortunately when doing some test cross-compiles on arm I hit the
> > following build failure:
> >
> > kernel/seccomp.c: In function '__secure_computing':
> > kernel/seccomp.c:55:23: error: 'NR_syscalls' undeclared (first use in this function)
> > kernel/seccomp.c:55:23: note: each undeclared identifier is reported only once for each function it appears in
> > make[3]: *** [kernel/seccomp.o] Error 1
> >
> > This is actually the same build error we were seeing in Oneiric when
> > trying to enable seccomp on arm [1].  Care to send a patch to fix this
> > up?  For now I've temporarily disabled the seccomp patches on arm in our
> > ubuntu-precise git repo.
> >
> > Thanks,
> > Leann
> >
> > [1] https://lists.ubuntu.com/archives/kernel-team/2011-August/016749.html
> >
> >
> 
> 
> 






More information about the kernel-team mailing list