From: Stephen Smalley <sds@tycho.nsa.gov>
To: "Kovacsics Róbert" <kovirobi@gmail.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: policycoreutils build error
Date: Tue, 21 Feb 2012 15:33:39 -0500 [thread overview]
Message-ID: <1329856419.12501.78.camel@moss-pluto> (raw)
In-Reply-To: <CABPkNKmB6ZdGtT1Avy64sFxce1y1WqAzD73uwZTqF8ij6c4t0w@mail.gmail.com>
On Sat, 2012-02-11 at 13:13 +0000, Kovacsics Róbert wrote:
> Hello all!
>
> I would like to ask for assistance on compiling SELinux (particularly
> policycoreutils 2.1.0)
>
> Here is my setup:
> *Linux from scratch running kernel 3.2.5
> *Installed libsepol
> *Installed libselinux
> *Installed libsemanage
> *Installed sepolgen
> *Installed checkpolicy
>
> Error on installing policycoreutils-2.1.0
> Error:
> make[1]: Entering directory
> `/blfs-sources/selinux/policycoreutils-2.1.0/sandbox'
> cc -I/usr/include -DPACKAGE="\"policycoreutils\"" -c -o seunshare.o
> seunshare.c
> seunshare.c: In function ‘main’:
> seunshare.c:242:21: error: ‘CLONE_NEWNS’ undeclared (first use in this function)
> seunshare.c:242:21: note: each undeclared identifier is reported only
> once for each function it appears in
> make[1]: *** [seunshare.o] Error 1
> make[1]: Leaving directory `/blfs-sources/selinux/policycoreutils-2.1.0/sandbox'
> make: *** [all] Error 1
$ grep CLONE_NEWNS /usr/include/*/*.h
/usr/include/bits/sched.h:# define CLONE_NEWNS 0x00020000 /* Set to create new namespace. */
/usr/include/linux/sched.h:#define CLONE_NEWNS 0x00020000 /* New namespace group? */
--
Stephen Smalley
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2012-02-21 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 13:13 Kovacsics Róbert
2012-02-21 20:33 ` Stephen Smalley [this message]
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=1329856419.12501.78.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=SELinux@tycho.nsa.gov \
--cc=kovirobi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.