All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Chad Sellers <csellers@tresys.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: This patch fixes the exception handling in libselinux-python bindings
Date: Wed, 16 Sep 2009 15:18:00 -0400	[thread overview]
Message-ID: <4AB139E8.50700@manicmethod.com> (raw)
In-Reply-To: <4A830B34.60402@redhat.com>



Daniel J Walsh wrote:
> What do you think of this one.  Removed excess swig cruft,
>
> You need to run
>
> make swigify to generate those changes.
>

Ok, looking at this now. I don't completely get how it works. I'm trying 
to reproduce what you are doing by hand but nothing comes out of gcc:

[root@localhost src]# echo '#include "../include/selinux/selinux.h"' > 
temp.c
[root@localhost src]# gcc -c temp.c -aux-info temp.aux
[root@localhost src]# ls temp.*
temp.c  temp.o


What is the purpose of the aux-info thing, and why doesn't it work on my 
F11 machine?

also, I'm not sure if the best place for selinuxswig_exception.i is 
swigify or pywrap. In the swigify case it shouldn't be in the clean 
target because if you check out the repo and do make clean; make pywrap 
you'll get an error. (I can make these fixes, I'm just trying to figure 
out how it all works first).


--
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.

  reply	other threads:[~2009-09-16 19:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C6A74D22.A99BD%csellers@tresys.com>
2009-08-12 18:34 ` This patch fixes the exception handling in libselinux-python bindings Daniel J Walsh
2009-09-16 19:18   ` Joshua Brindle [this message]
2009-09-16 19:35     ` Joshua Brindle
     [not found]       ` <4AB15164.1020507@redhat.com>
2009-09-24  0:56         ` Joshua Brindle
2009-09-24 18:16           ` Joshua Brindle
2009-09-24 19:19             ` Joshua Brindle
2009-09-28 19:07               ` Daniel J Walsh
2009-09-28 20:10                 ` Joshua Brindle
2010-01-08 15:32                 ` Stephen Smalley
2010-01-08 20:06                   ` Stephen Smalley
2010-01-08 20:19                     ` Stephen Smalley
2010-01-08 20:40                       ` Daniel J Walsh
2010-01-08 20:52                         ` Joshua Brindle
2010-02-08 21:10                           ` Caleb Case
2010-03-06 23:23                             ` Joshua Brindle
2009-05-18 18:10 Daniel J Walsh
2009-05-19 16:16 ` Chad Sellers
2009-05-19 17:35   ` Daniel J Walsh
2009-06-18 14:23     ` Joshua Brindle
2009-06-18 19:41       ` Daniel J Walsh

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=4AB139E8.50700@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=csellers@tresys.com \
    --cc=dwalsh@redhat.com \
    --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.