From: William Roberts <bill.c.roberts@gmail.com>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: Joshua Brindle <joshua.brindle@crunchydata.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
SElinux list <selinux@vger.kernel.org>,
William Roberts <william.c.roberts@intel.com>
Subject: Re: [PATCH] cil: drop remaining dso.h include
Date: Thu, 26 Mar 2020 11:51:49 -0500 [thread overview]
Message-ID: <CAFftDdoxp1ARDubfAQ0jMZeeVHqjGzq0bP-mv91ry4xWMgXDUA@mail.gmail.com> (raw)
In-Reply-To: <CAEjxPJ4R_oxqTkVFcHRyWVC3_Sn9zVuPZbvJbcW1iuf7uskkqw@mail.gmail.com>
On Thu, Mar 26, 2020 at 11:49 AM Stephen Smalley
<stephen.smalley.work@gmail.com> wrote:
>
> On Thu, Mar 26, 2020 at 11:17 AM Joshua Brindle
> <joshua.brindle@crunchydata.com> wrote:
> > It looks like this change broke building on MacOS:
> >
> > <inline asm>:1:1: error: unknown directive
> > .symver cil_build_policydb_pdb, cil_build_policydb@LIBSEPOL_1.0
> > ^
> >
> > (on all of them).
> >
> > Previously dso.h defined DISABLE_SYMVER for Android and Apple, is
> > support for those intended to go away?
>
> Maybe we should add an osx build to our .travis.yml file and just test
> building libsepol/checkpolicy/secilc?
Definitely, I didn't realize travis had osx target. I can try and
queue this up for next week.
prev parent reply other threads:[~2020-03-26 16:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 15:25 libsepol drop dso.h bill.c.roberts
2020-03-09 15:25 ` [PATCH 1/2] libsepol/dso: drop hidden_proto and hidden_def bill.c.roberts
2020-03-10 20:10 ` Stephen Smalley
2020-03-10 20:15 ` William Roberts
2020-03-09 15:25 ` [PATCH 2/2] libsepol/Makefile: add -fno-semantic-interposition bill.c.roberts
2020-03-10 21:08 ` V2 libsepol drop dso.h bill.c.roberts
2020-03-10 21:08 ` [PATCH v2 1/3] libsepol/dso: drop hidden_proto and hidden_def bill.c.roberts
2020-03-10 21:08 ` [PATCH v2 2/3] libsepol/Makefile: add -fno-semantic-interposition bill.c.roberts
2020-03-10 21:08 ` [PATCH v2 3/3] lbespol: remove wild cards in mapfile bill.c.roberts
2020-03-11 18:53 ` Stephen Smalley
2020-03-11 18:54 ` Stephen Smalley
2020-03-12 13:59 ` William Roberts
2020-03-12 20:22 ` Stephen Smalley
2020-03-12 21:42 ` William Roberts
2020-03-13 11:03 ` Ondrej Mosnacek
2020-03-13 14:22 ` William Roberts
2020-03-13 14:41 ` Ondrej Mosnacek
2020-03-13 14:51 ` William Roberts
2020-03-17 17:46 ` Stephen Smalley
2020-03-19 19:46 ` William Roberts
2020-03-19 19:48 ` [PATCH] cil: drop remaining dso.h include bill.c.roberts
2020-03-20 8:08 ` Ondrej Mosnacek
2020-03-23 15:35 ` William Roberts
2020-03-26 15:16 ` Joshua Brindle
2020-03-26 15:35 ` William Roberts
2020-03-26 15:46 ` cil: Fix DISABLE_SYMVER support and drop last dso.h bill.c.roberts
2020-03-26 15:46 ` [PATCH 1/2] cil: rm dead dso.h file bill.c.roberts
2020-03-26 15:46 ` [PATCH 2/2] cil: re-enable DISABLE_SYMVER define bill.c.roberts
2020-03-26 15:47 ` cil: Fix DISABLE_SYMVER support and drop last dso.h William Roberts
2020-03-26 16:05 ` Joshua Brindle
2020-03-26 16:18 ` William Roberts
2020-03-27 14:27 ` William Roberts
2020-03-27 14:47 ` Stephen Smalley
2020-03-27 15:02 ` William Roberts
2020-03-26 16:50 ` [PATCH] cil: drop remaining dso.h include Stephen Smalley
2020-03-26 16:51 ` William Roberts [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=CAFftDdoxp1ARDubfAQ0jMZeeVHqjGzq0bP-mv91ry4xWMgXDUA@mail.gmail.com \
--to=bill.c.roberts@gmail.com \
--cc=joshua.brindle@crunchydata.com \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=william.c.roberts@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).