From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Stephen Smalley <stephen.smalley@gmail.com>
Cc: SE-Linux <selinux@tycho.nsa.gov>, tresys <refpolicy@oss1.tresys.com>
Subject: Re: ERROR 'syntax error' at token ':c' on line 42:
Date: Tue, 12 Oct 2010 07:32:21 -0700 [thread overview]
Message-ID: <4CB47175.6020302@gmail.com> (raw)
In-Reply-To: <AANLkTi=RFa1UkhfHuq_dUUYaNaPD1yWnDwRQ+wZ8p-C_@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
On 10/12/2010 04:39 AM, Stephen Smalley wrote:
> Looks like the previously discussed flex bug, e.g.:
> http://marc.info/?l=selinux&m=126763385807985&w=2
>
yeah I was thinking this as well.. from what it seems this is hitting
with the
packages provided by suse, as well as the userspace packages. but unlike
my other system that was hitting this, the error is with building a
module, instead of building
the policy.(as a workaround I would throw in an older version of flex,
then build only
checkpolicy/module to get it working..(or if I was too lazy just copy a
version that
works over to the other machine)).
I can go through this today and see what I get.. one thing I noticed
with the packages
from suse(11.4) is, policycoreutils is older than same of the newer
packages they have,
causing other errors with python i.e. seinfo not found kind of error.
As for flex itself.. I do remember starting a bisect on that package,
but then realized
that from version 2.34(if I remember correctly) to 2.35 theirs just a
few patches that
are rather lengthy, making a bisect possible, but then going through the
bad commit
more lengthy...
Justin P. Mattock
[-- Attachment #2: Type: text/html, Size: 1941 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] ERROR 'syntax error' at token ':c' on line 42:
Date: Tue, 12 Oct 2010 07:32:21 -0700 [thread overview]
Message-ID: <4CB47175.6020302@gmail.com> (raw)
In-Reply-To: <AANLkTi=RFa1UkhfHuq_dUUYaNaPD1yWnDwRQ+wZ8p-C_@mail.gmail.com>
On 10/12/2010 04:39 AM, Stephen Smalley wrote:
> Looks like the previously discussed flex bug, e.g.:
> http://marc.info/?l=selinux&m=126763385807985&w=2
>
yeah I was thinking this as well.. from what it seems this is hitting
with the
packages provided by suse, as well as the userspace packages. but unlike
my other system that was hitting this, the error is with building a
module, instead of building
the policy.(as a workaround I would throw in an older version of flex,
then build only
checkpolicy/module to get it working..(or if I was too lazy just copy a
version that
works over to the other machine)).
I can go through this today and see what I get.. one thing I noticed
with the packages
from suse(11.4) is, policycoreutils is older than same of the newer
packages they have,
causing other errors with python i.e. seinfo not found kind of error.
As for flex itself.. I do remember starting a bisect on that package,
but then realized
that from version 2.34(if I remember correctly) to 2.35 theirs just a
few patches that
are rather lengthy, making a bisect possible, but then going through the
bad commit
more lengthy...
Justin P. Mattock
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.tresys.com/pipermail/refpolicy/attachments/20101012/46fd43a0/attachment.html
next prev parent reply other threads:[~2010-10-12 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 6:17 ERROR 'syntax error' at token ':c' on line 42: Justin Mattock
2010-10-10 6:17 ` [refpolicy] " Justin Mattock
2010-10-11 12:29 ` Christopher J. PeBenito
2010-10-11 12:29 ` Christopher J. PeBenito
2010-10-11 18:02 ` Justin P. Mattock
2010-10-11 18:02 ` Justin P. Mattock
2010-10-12 11:39 ` Stephen Smalley
2010-10-12 14:32 ` Justin P. Mattock [this message]
2010-10-12 14:32 ` [refpolicy] " 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=4CB47175.6020302@gmail.com \
--to=justinmattock@gmail.com \
--cc=refpolicy@oss1.tresys.com \
--cc=selinux@tycho.nsa.gov \
--cc=stephen.smalley@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.