From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>, Karl MacMillan <kmacmillan@tresys.com>
Subject: Re: Busted by constraints.
Date: Tue, 17 May 2005 08:41:39 -0400 [thread overview]
Message-ID: <4289E683.1030702@redhat.com> (raw)
In-Reply-To: <1116329977.917.7.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Mon, 2005-05-16 at 18:00 -0400, Daniel J Walsh wrote:
>
>
>>I think, this patch is needed to export symbols of newly added libsepol
>>functions.
>>
>>
>
>No. These particular functions are _only_ for the static library and
>programs that link with it, as they expose too much of the internals of
>libsepol. Note that audit2why is linked with libsepol.a, not the shared
>library (prior to your policycoreutils patch). We will not _export_
>these symbols via the shared library.
>
>
>
Ok libdir needs to be passed in via spec file.
Dan
--
--
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:[~2005-05-17 12:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 14:32 Busted by constraints Daniel J Walsh
2005-05-12 14:30 ` Stephen Smalley
2005-05-12 14:46 ` Daniel J Walsh
2005-05-13 15:00 ` Stephen Smalley
2005-05-13 19:30 ` Stephen Smalley
2005-05-13 20:00 ` Stephen Smalley
2005-05-16 18:44 ` Stephen Smalley
2005-05-16 22:00 ` Daniel J Walsh
2005-05-17 11:39 ` Stephen Smalley
2005-05-17 11:50 ` Stephen Smalley
2005-05-17 12:41 ` Daniel J Walsh [this message]
2005-05-17 12:05 ` Stephen Smalley
2005-05-13 15:35 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 20:37 Casey Schaufler
2005-05-13 11:16 ` Stephen Smalley
2005-05-13 15:10 Casey Schaufler
2005-05-13 15:20 ` Stephen Smalley
2005-05-13 15:56 Casey Schaufler
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=4289E683.1030702@redhat.com \
--to=dwalsh@redhat.com \
--cc=kmacmillan@tresys.com \
--cc=sds@tycho.nsa.gov \
--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.