From: Joshua Brindle <method@manicmethod.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [PATCH] [STABLE] Makefile change to disable restorecond
Date: Wed, 12 Dec 2007 10:09:45 -0500 [thread overview]
Message-ID: <475FF9B9.20005@manicmethod.com> (raw)
In-Reply-To: <1197404396.28006.111.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Tue, 2007-12-11 at 15:13 -0500, Joshua Brindle wrote:
>
>> Joshua Brindle wrote:
>>
>>> This patch is necessary to build stable on RHEL4. CLIP uses the
>>> current stable toolchain and supports RHEL4 as a target so we are
>>> trying to upstream any magic that is necessary to build on that platform.
>>>
>>>
>> Ignore last patch, this one is actually against stable :)
>>
>
> What about just checking for the presence of /usr/include/sys/inotify.h
> and disabling restorecond in its absence, similar to handling of PAMH
> and AUDITH in newrole's Makefile? Then that could go into trunk too.
>
The next problem is that libselinux won't build on RHEL4 without
building the .lo files with --ftls-model=initial-exec. Do you have an
opinion on how to switch this on/off for building there?
--
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:[~2007-12-12 15:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 20:05 [PATCH] [STABLE] Makefile change to disable restorecond Joshua Brindle
2007-12-11 20:13 ` Joshua Brindle
2007-12-11 20:19 ` Stephen Smalley
2007-12-12 0:07 ` Joshua Brindle
2007-12-12 15:40 ` Stephen Smalley
2007-12-12 15:09 ` Joshua Brindle [this message]
2007-12-12 15:35 ` Stephen Smalley
2007-12-12 16:02 ` Joshua Brindle
2007-12-12 16:11 ` Stephen Smalley
2007-12-12 16:42 ` Joshua Brindle
2007-12-12 16:47 ` Stephen Smalley
2007-12-12 16:59 ` Joshua Brindle
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=475FF9B9.20005@manicmethod.com \
--to=method@manicmethod.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.