From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Sven Vermeulen <sven.vermeulen@siphos.be>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: [PATCH/RFC] setools: update swig interfaces for swig-2.0.7 (and higher?)
Date: Wed, 29 Aug 2012 11:00:29 -0400 [thread overview]
Message-ID: <503E2E8D.2020606@tresys.com> (raw)
In-Reply-To: <CAPzO=NwR-7KruhfYYRO+SFGD2=cmuG+w5dNPaqbz=UhiJ4=Ziw@mail.gmail.com>
On 08/25/12 12:47, Sven Vermeulen wrote:
> On Fri, Aug 24, 2012 at 7:17 PM, Eric Paris <eparis@parisplace.org> wrote:
>> With your patch does it still build with the old swig version? I know
>> we put a nasty hack in Fedora which made it build with new swig, but
>> wouldn't build with old swig.
>
> It builds fine with swig-2.* (tested with 2.0.3, 2.0.4, 2.0.7 and now 2.0.8).
>
> swig-1.3.40 doesn't, but without my patch it fails with 1.3.40 as well.
As an upstream matter, I'm not sure that we care if it fails with the old swig. 2.* has been out for a few years, right?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
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:[~2012-08-29 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 16:15 [PATCH/RFC] setools: update swig interfaces for swig-2.0.7 (and higher?) Guido Trentalancia
2012-08-24 16:18 ` Sven Vermeulen
2012-08-24 17:17 ` Eric Paris
2012-08-25 16:47 ` Sven Vermeulen
2012-08-29 15:00 ` Christopher J. PeBenito [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-20 19:07 Sven Vermeulen
2012-09-05 17:37 ` Christopher J. PeBenito
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=503E2E8D.2020606@tresys.com \
--to=cpebenito@tresys.com \
--cc=selinux@tycho.nsa.gov \
--cc=sven.vermeulen@siphos.be \
/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.