From: Stephen Smalley <sds@tycho.nsa.gov>
To: wenzong.fan@windriver.com, selinux@tycho.nsa.gov
Subject: Re: [PATCH] libselinux: get pywrap depends on selinux.py
Date: Tue, 25 Aug 2015 15:05:28 -0400 [thread overview]
Message-ID: <55DCBC78.30509@tycho.nsa.gov> (raw)
In-Reply-To: <1439539721-25847-1-git-send-email-wenzong.fan@windriver.com>
On 08/14/2015 04:08 AM, wenzong.fan@windriver.com wrote:
> From: Wenzong Fan <wenzong.fan@windriver.com>
>
> The selinux.py is generated at compile-time and will be installed as
> python module "selinux/__init__.py", just make sure that it has been
> generated completely while starting "make install-pywrap".
>
> This fixes below errors that caused by an empty "selinux/__init__.py":
>
> $ /usr/sbin/semanage -h
>
> Traceback (most recent call last):
> File "/usr/sbin/semanage", line 30, in <module>
> import seobject
> File "/usr/lib64/python2.7/site-packages/seobject.py", line 27, in <module>
> import sepolicy
> File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 226, in <module>
> def get_file_equiv_modified(fc_path = selinux.selinux_file_context_path()):
> AttributeError: 'module' object has no attribute 'selinux_file_context_path'
>
> Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
> ---
> libselinux/src/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libselinux/src/Makefile b/libselinux/src/Makefile
> index ac25c1f..a81acc7 100644
> --- a/libselinux/src/Makefile
> +++ b/libselinux/src/Makefile
> @@ -90,7 +90,7 @@ SWIGRUBY = swig -Wall -ruby -o $(SWIGRUBYCOUT) -outdir ./
>
> all: $(LIBA) $(LIBSO) $(LIBPC)
>
> -pywrap: all $(SWIGSO) $(AUDIT2WHYSO)
> +pywrap: all $(SWIGFILES) $(AUDIT2WHYSO)
>
> rubywrap: all $(SWIGRUBYSO)
Thanks, applied.
prev parent reply other threads:[~2015-08-25 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 8:08 [PATCH] libselinux: get pywrap depends on selinux.py wenzong.fan
2015-08-25 19:05 ` Stephen Smalley [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=55DCBC78.30509@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=wenzong.fan@windriver.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.