All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: sure <mengshuo@gmail.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: About compile an appplication's policy
Date: Fri, 05 Nov 2010 08:07:10 -0400	[thread overview]
Message-ID: <4CD3F36E.3040309@tresys.com> (raw)
In-Reply-To: <AANLkTiknqsWLqo2M+dpr75rDHG4jE-ei+Rm4mDC61PS3@mail.gmail.com>

On 11/04/10 22:19, sure wrote:
> Hi :    
>       I am trying to create my own policy module, but i met with a
> problem: after i finished the myapp.te, myapp.if and myapp.fc in my
> directory named mypolicy, I copied the uncompress
> refpolicy-20070928.tar.bz2 dir ../refpolicy/doc/Makefile.example to
> ../mypolicy and renamed Makefile, then i tried to "make" , it gave such
> wrong info:
> 
> Makefile:8: /usr/share/selinux/devel/mls/include/Makefile: No such file
> or directory
> make: *** No rule to make target
> `/usr/share/selinux/devel/mls/include/Makefile'.  Stop.
> 
> then i check the dir /usr/share/selinux/devel/mls/ , there are many *.pp
> files in, but  no directory named include, should i install some other
> package or find it in somewhere else.

What version of Red Hat/Fedora are you using?  I believe some of the
older ones had these files in the selinux-policy-devel package.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

--
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.

  reply	other threads:[~2010-11-05 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05  2:19 About compile an appplication's policy sure
2010-11-05 12:07 ` Christopher J. PeBenito [this message]
2010-11-08  1:46   ` sure

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=4CD3F36E.3040309@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=mengshuo@gmail.com \
    --cc=selinux@tycho.nsa.gov \
    /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.