All of lore.kernel.org
 help / color / mirror / Atom feed
From: stefan@seekline.net (Stefan Schulze Frielinghaus)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Undefined policycap error
Date: Fri, 25 Sep 2009 15:54:41 +0200	[thread overview]
Message-ID: <1253886881.29190.2.camel@localhost> (raw)
In-Reply-To: <F881A5D7AE676240B733682CA6DC509605A68924@XMBIL103.northgrum.com>

I guess you are out of luck on RHEL because of build dependencies:

http://oss.tresys.com/projects/refpolicy/wiki/DownloadRelease

Reference Policy has the following build-time dependencies for modular
policies:

      * Checkpolicy 2.0.16 or higher
      * Policycoreutils 2.0 or higher
      * Libsepol 2.0.29 or higher
      * Libsemanage-2.0.29 or higher
      * Python PyXML (only required to regenerate config files and
        documentation)

On Fri, 2009-09-25 at 08:13 -0500, Kane, Bob (IS) wrote:
> Downloaded the most recent Reference policy source
> (refpolicy-2.20090730.tar.bz2)  and I am trying to build and install
> the policy on a standard RHEL 5.3 platform.  When doing a make or make
> all, I receive the following:
> 
> (unknown source)::ERROR ?syntax error? at token ?policycap? on line
> 1757:
> 
> #
> 
> policycap network_peer_controls;
> 
> ?
> 
> ?
> 
> Any ideas?  Is there any way to search the archive in case this has
> already been answered?
> 
> Bob
> 
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy

  reply	other threads:[~2009-09-25 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 13:13 [refpolicy] Undefined policycap error Kane, Bob (IS)
2009-09-25 13:54 ` Stefan Schulze Frielinghaus [this message]
     [not found]   ` <F881A5D7AE676240B733682CA6DC509605A689E2@XMBIL103.northgrum.com>
2009-09-25 15:03     ` Stefan Schulze Frielinghaus
2009-09-25 21:54       ` Brandon Whalen

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=1253886881.29190.2.camel@localhost \
    --to=stefan@seekline.net \
    --cc=refpolicy@oss.tresys.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.