From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Chris PeBenito <pebenito@gentoo.org>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: libselinux swig wrapper breakage
Date: Mon, 20 Feb 2006 02:22:54 -0500 [thread overview]
Message-ID: <43F96E4E.6020704@cornell.edu> (raw)
In-Reply-To: <1140408745.8756.31.camel@gorn.pebenito.net>
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> TypeError: argument number 1: a 'security_context_t *' is expected, 'str(user_u:user_r:user_spamassassin_t)' is received
>
You're passing a string into something that expects a security_context_t.
That won't work - it fails, because security_context_t is an opaque
type, and swig has no idea that it represents a char*. It would know
that if selinux.h was included in the interface file. However, the swig
bindings for selinux take the approach of listing all the functions
manually (and omitting the public definition of security_context_t as a
char*).
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-02-20 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 4:12 libselinux swig wrapper breakage Chris PeBenito
2006-02-20 7:22 ` Ivan Gyurdiev [this message]
2006-02-20 7:31 ` Ivan Gyurdiev
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=43F96E4E.6020704@cornell.edu \
--to=ivg2@cornell.edu \
--cc=pebenito@gentoo.org \
--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.