All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janak Desai <janak@us.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Manoj Srivastava <manoj.srivastava@stdc.com>,
	Janak Desai <jdesai@us.ibm.com>,
	selinux@tycho.nsa.gov
Subject: Re: libselinux does not compile on ia64
Date: Mon, 08 Aug 2005 09:03:36 -0400	[thread overview]
Message-ID: <42F75828.1090700@us.ibm.com> (raw)
In-Reply-To: <1123504573.13654.113.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Sat, 2005-08-06 at 08:49 -0500, Manoj Srivastava wrote:
> 
>>Hi,
>>
>>
>>	The latest libselinux fails to compile on IA64 with the
>> following error:
>> cc -Wall -I../include -D_GNU_SOURCE    setupns.c  -L../src -lselinux  -o setupn
>> setupns.c:17: error: syntax error before "clone"
>> setupns.c:22: warning: return type defaults to `int'
>>
>>        Apparently, there is no clone on IA64.  There is an excerpt
>> from libc 2.3.2 that implements a clone look alike for IA64; however,
>> libc is LGPL'd , so the combination is no longer public domain.
> 
> 
> At this point, I think setupns in libselinux is obsoleted by Janak's
> patches for pam.  Right, Janak?  So we could just drop it altogether,
> both utils/setupns.c (example utility) and src/setupns.c (libselinux
> function).  There are no users of it yet.
> 

Yup. That's correct. We can drop setupns() from both utils/setupns.c and
src/setupns.c. Functionality provided by setupns() has migrated to the
pam_namespace patch.

-Janak


--
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.

  reply	other threads:[~2005-08-08 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06 13:49 libselinux does not compile on ia64 Manoj Srivastava
2005-08-08 12:36 ` Stephen Smalley
2005-08-08 13:03   ` Janak Desai [this message]
2005-08-11 15:01     ` Stephen Smalley
2005-08-22  7:39 ` Florian Weimer

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=42F75828.1090700@us.ibm.com \
    --to=janak@us.ibm.com \
    --cc=jdesai@us.ibm.com \
    --cc=manoj.srivastava@stdc.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.