All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Russell Coker <russell@coker.com.au>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Mix and Match problems
Date: Sun, 24 Mar 2002 15:22:23 +0000	[thread overview]
Message-ID: <20020324152223.GM20057@vnl.com> (raw)
In-Reply-To: <20020322212840.CF3FE108F@lyta.coker.com.au>

A question for Russ. In your debian package you still
have the original policy/README file. If you are 
trying to build an selinux using your policy Makefile
there is a catch-22. The README suggests building
and installing policy first; but your Makefile uses
chsid. chsid is not built until the next step when
you make and make install libsecure; and even then
it would not ordinarily be built as the original 
libsecure/test/Makefile suggests it is needed only 
if chcon is not present.

After going through that, I still got errors when
trying to use your make install. I'm going to 
presume that is due to the fact that I'm doing
a build under a non-selinux kernel and thus
chsid is missing something it needs.

This may all be moot, and I'm getting the problems
only because I'm mixing your policy with Stephen's
release, but thought I'd mention it in case it's
of any use.


--
You have received this message because you are subscribed to the selinux 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:[~2002-03-24 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 21:28 strange failure Russell Coker
2002-03-24 15:22 ` Dale Amon [this message]
2002-03-25  0:30   ` Mix and Match problems Russell Coker
2002-03-25 13:57 ` strange failure Stephen Smalley

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=20020324152223.GM20057@vnl.com \
    --to=amon@vnl.com \
    --cc=russell@coker.com.au \
    --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.