From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Building refpolicy fails on Arch Linux
Date: Fri, 2 Sep 2011 10:16:33 -0400 [thread overview]
Message-ID: <4E60E541.1030707@tresys.com> (raw)
In-Reply-To: <1851802.b6gYmqOXcx@hikari>
On 08/31/11 14:15, Nicky726 wrote:
> Dne P?? 19. srpna 2011 11.07:58 jste napsal(a):
>> Actually its Gentoo's version. I haven't heard any problems from Dan
>> about compile errors like this in Fedora, so I'm still thinking its your
>> toolchain. Did you rebuild checkpolicy after changing flex and bison?
>> This pops up from time to time, the last thread I can find on it is here:
>>
>> http://marc.info/?l=selinux&m=126762983301065&w=2
>>
>> Also cc'ing Steve Smalley in case he has any additional feedback.
>>
>> Steve: maybe we should put up a page on the selinuxproject.org about
>> these flex issues. Maybe a summary of what we know or known bad
>> versions or something.
>
> I tried various combinations of versions of flex, bison and selinux userspace. I didn't succede on my SELinux netbook. I managed to build refpolicy on my
> primary machine with just latest SELinux Userspace and prehistoric flex (2.5.4a-4), that is version combination which does not build the policy on my
> netbook. I don't quite get it, especially as the software configuration is quite alike.
Unfortunately all I can suggest is to try the SELinux list for further help. They'll be better able to sort out any toolchain issues you may have.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-09-02 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 12:00 [refpolicy] Building refpolicy fails on Arch Linux Nicky726
2011-08-19 12:14 ` Christopher J. PeBenito
2011-08-19 13:21 ` Nicky726
2011-08-19 15:07 ` Christopher J. PeBenito
2011-08-31 18:15 ` Nicky726
2011-09-02 14:16 ` Christopher J. PeBenito [this message]
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=4E60E541.1030707@tresys.com \
--to=cpebenito@tresys.com \
--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.