From: Justin Friel <capn_shoe@yahoo.com>
To: SELinux@tycho.nsa.gov
Subject: Re: Trouble building Policy-1.16
Date: Wed, 25 Aug 2004 15:23:22 -0700 (PDT) [thread overview]
Message-ID: <20040825222322.32725.qmail@web60002.mail.yahoo.com> (raw)
In-Reply-To: <1093439988.6743.77.camel@moss-spartans.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 2759 bytes --]
--- Stephen Smalley <sds@epoch.ncsc.mil> wrote:
> On Tue, 2004-08-24 at 15:25, Justin Friel wrote:
> > I am having a hard time getting policy-1.16 to
> compile
> > on a "Linux from scratch" system. When I try to
> > compile the strict policy, I get the following
> output:
> >
> > ...
> > /usr/bin/checkpolicy -o policy.18 policy.conf
> > /usr/bin/checkpolicy: loading policy
> configuration
> > from policy.conf
> > types/file.te:92:ERROR 'syntax error' at token
> ':f' on
> > line 3066:
> > allow auth shadow_t:file { getattr read };
> > type shadow_t, file_type;
> > /usr/bin/checkpolicy: error(s) encountered while
> > parsing configuration
> > make: *** [policy.18] Error 1
>
> That looks very odd. Can you send your entire
> policy.conf file to me?
Sorry if this is a repost, I sent this in earlier this
morning and haven't seen it hit the list yet.
I bzipped and attached the policy.conf. As for the
warnings while bulding checkpoliy, they seem harmless
to me, but here they are.
yacc -d policy_parse.y
cc -g -Wall -O2 -pipe -I. -o y.tab.o -c y.tab.c
y.tab.c: In function `yyparse':
y.tab.c:1693: warning: implicit declaration of
function `yylex'
policy_parse.y:724: warning: implicit declaration of
function `strtoul'
policy_parse.y: In function `insert_id':
policy_parse.y:766: warning: implicit declaration of
function `free'
lex policy_scan.l
cc -g -Wall -O2 -pipe -I. -o lex.yy.o -c lex.yy.c
lex.yy.c: In function `yylex':
lex.yy.c:1457: warning: label `find_rule' defined but
not used
policy_scan.l: At top level:
lex.yy.c:2308: warning: `yyunput' defined but not used
lex.yy.c:2918: warning: `yy_flex_strlen' defined but
not used
cc -g -Wall -O2 -pipe -I. -o queue.o -c queue.c
cc -g -Wall -O2 -pipe -I. -o checkpolicy.o -c
checkpolicy.c
cc -o checkpolicy y.tab.o lex.yy.o queue.o
checkpolicy.o -lfl /usr/lib/libsepol.a
yacc -d -o users.tab.c users.y
cc -g -Wall -O2 -pipe -I. -o users.tab.o -c
users.tab.c
users.tab.c: In function `yyparse':
users.tab.c:961: warning: implicit declaration of
function `yylex'
users.y: In function `insert_id':
users.y:139: warning: implicit declaration of function
`free'
lex -olex.users.c users.l
cc -g -Wall -O2 -pipe -I. -o lex.users.o -c
lex.users.c
lex.users.c: In function `yylex':
lex.users.c:782: warning: label `find_rule' defined
but not used
users.l: At top level:
lex.users.c:1178: warning: `yyunput' defined but not
used
lex.users.c:1788: warning: `yy_flex_strlen' defined
but not used
cc -g -Wall -O2 -pipe -I. -o genpolusers.o -c
genpolusers.c
cc -o genpolusers users.tab.o lex.users.o queue.o
genpolusers.o -lfl /usr/lib/libsepol.a
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
[-- Attachment #2: policy.conf.bz2 --]
[-- Type: application/x-tar, Size: 257903 bytes --]
next parent reply other threads:[~2004-08-26 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1093439988.6743.77.camel@moss-spartans.epoch.ncsc.mil>
2004-08-25 22:23 ` Justin Friel [this message]
2004-08-26 12:56 ` Trouble building Policy-1.16 Stephen Smalley
2004-08-26 14:07 ` James Morris
2004-08-26 16:12 ` Justin Friel
2004-08-26 16:21 ` Stephen Smalley
2004-08-26 22:53 ` Luke Kenneth Casson Leighton
2004-08-26 23:57 ` Justin Friel
2004-08-27 14:26 ` Luke Kenneth Casson Leighton
2004-08-27 17:18 ` Dale Amon
2004-08-27 22:01 ` Luke Kenneth Casson Leighton
2004-08-24 19:25 Justin Friel
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=20040825222322.32725.qmail@web60002.mail.yahoo.com \
--to=capn_shoe@yahoo.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.