All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikram Noel Ambrose <noel.ambrose@gmail.com>
To: Jason Tang <jtang@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>, Joshua Brindle <jbrindle@tresys.com>
Subject: Re: [autotools] libselinux build system comments
Date: Mon, 29 Sep 2008 15:35:38 -0400	[thread overview]
Message-ID: <48E12E0A.3000604@gmail.com> (raw)
In-Reply-To: <06A6610D4F464D4EBEAFBF2C5F86911E669857@exchange2.columbia.tresys.com>

Jason Tang wrote:
> From: owner-selinux@tycho.nsa.gov on behalf of Vikram Noel Ambrose
> Sent: Sat 2008-09-27 22:28
> To: SE Linux
> Subject: Re: [autotools] libselinux build system comments
>  
>   
>>> libselinux and libsepol should be installed to /lib (or /lib64).  The reason is because /usr/lib may be on a different 
>>> filesystem, but /lib (and /lib64) is nearly guaranteed to be available by the time the system will load the SELinux policy.
>>>       
>
>   
>> And ./configure --libdir=/lib64. doesnt solve this?
>>     
>
> No, because then libsemanage would be installed to the wrong location.
>
>   
Sorry I don't follow, do you mean all the sub-packages need to be 
compiled with the same configure parameters?

--
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:[~2008-09-29 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 19:40 [autotools] libselinux build system comments Jason Tang
2008-09-27 16:49 ` Vikram Noel Ambrose
2008-09-27 22:28   ` Jason Tang
2008-09-28  2:28     ` Vikram Noel Ambrose
2008-09-29 15:06       ` Jason Tang
2008-09-29 19:35         ` Vikram Noel Ambrose [this message]
2008-09-29 15:13       ` 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=48E12E0A.3000604@gmail.com \
    --to=noel.ambrose@gmail.com \
    --cc=jbrindle@tresys.com \
    --cc=jtang@tresys.com \
    --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.