From: Eric Laganowski <eric@laganowski.net>
To: selinux@tycho.nsa.gov
Subject: Re: 'make policy' issues
Date: Wed, 21 Oct 2009 11:18:59 -0400 [thread overview]
Message-ID: <4ADF2663.2030105@laganowski.net> (raw)
In-Reply-To: <1256138160.4061.200.camel@moss-pluto.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2009-10-21 at 11:06 -0400, Eric Laganowski wrote:
>
>> Hello,
>>
>> I was trying to build selinux userspace tools on my custom linux build.
>> Everything went fine until I attempted to compile reference policy.
>> Could you please help me in understanding what went wrong here.
>>
>> refpolicy-2.20090730
>>
>> $ make policy
>> Compiling refpolicy policy.24
>> /usr/bin/checkpolicy policy.conf -o policy.24
>> /usr/bin/checkpolicy: loading policy configuration from policy.conf
>> policy/modules/kernel/corenetwork.te":1715:ERROR 'syntax error' at token ':' on line 9122:
>> allow corenet_unconfined_type node_type:node *;
>>
>> checkpolicy: error(s) encountered while parsing configuration
>> make: *** [policy.24] Error 1
>>
>>
>> Packages:
>>
>> checkpolicy-2.0.19
>> libselinux-2.0.85
>> libsemanage-2.0.33
>> libsepol-2.0.37
>> policycoreutils-2.0.69
>> sepolgen-1.0.17
>>
>> $ yacc -V
>> yacc - 1.9 20090221
>> $ flex -V
>> flex 2.5.35
>>
>
> Sounds similar to:
> http://marc.info/?l=selinux&m=117076095205821&w=2
>
> which was an upstream flex problem. However, I also see that you are using yacc rather than bison?
> Default for building checkpolicy is bison -y, which could be relevant.
>
Re bison/yacc: I tried both, byacc and 'bison -y'
Re flex: What is the requirement for flex from selinux perspective? Is
it known what build of flex is "known good"?
--
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.
next prev parent reply other threads:[~2009-10-21 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 15:06 'make policy' issues Eric Laganowski
2009-10-21 15:16 ` Stephen Smalley
2009-10-21 15:18 ` Eric Laganowski [this message]
2009-10-21 15:29 ` Stephen Smalley
2009-10-21 16:00 ` Justin P. Mattock
2009-10-21 16:22 ` Manoj Srivastava
2009-10-21 16:56 ` Eric Laganowski
2009-10-21 17:02 ` Stephen Smalley
2009-10-21 17:07 ` Eric Laganowski
2009-10-21 17:11 ` Stephen Smalley
2009-10-21 17:10 ` Eric Laganowski
2009-10-21 17:21 ` Mike Edenfield
2009-10-21 18:01 ` Justin P. Mattock
2009-11-16 22:09 ` Justin Mattock
2009-10-22 5:47 ` Manoj Srivastava
2009-10-22 7:18 ` Justin P. Mattock
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=4ADF2663.2030105@laganowski.net \
--to=eric@laganowski.net \
--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.