$ make conf
$ make policy
the second make made an error (in the attached file).
and also it generated policy.conf
On Thu, Jul 30, 2009 at 4:52 PM, Stephen Smalley <sds@xxxxxxxxxxxxx> wrote:
On Thu, 2009-07-30 at 09:51 +0430, mina elnino wrote:If you want to just unpack the source tree along with any
> well, i have to say that i went through the steps in:
>
> http://danwalsh.livejournal.com/26428.html
>
> and at last i realized that this page is for the ones who want to make
> policies from the source. now i have packages:
>
> $ ls ~/rpmbuild/RPMS/noarch/
> selinux-policy-3.6.12-62.fc11.noarch.rpm
> selinux-policy-doc-3.6.12-62.fc11.noarch.rpm
> selinux-policy-minimum-3.6.12-62.fc11.noarch.rpm
> selinux-policy-mls-3.6.12-62.fc11.noarch.rpm
> selinux-policy-targeted-3.6.12-62.fc11.noarch.rpm
>
> none of them is the source policy package. i mean i need that old m4
> macros, "*.te" files and "policy.conf" which could be installed by
> "selinux-policy-targeted-source" or "selinux-policy-strict-source" in
> fc4.
Fedora-specific patches applied, you can do:
rpm -i selinux-policy*.src.rpm
cd ~/rpmbuild/SPECS
rpmbuild -bp selinux-policy.spec
cd ../BUILD/serefpolicy*
Then you can build it in the usual manner.
You can also clone the upstream refpolicy repository if you want:
git clone http://oss.tresys.com/git/refpolicy.git
cd refpolicy
Note however that Fedora policy is built modular rather than monolithic,
so there is no policy.conf file per se. But if you run make with the
default build.conf, you'll end up with a policy.conf file.
--
Stephen Smalley
National Security Agency
Attachment:
result
Description: Binary data
