From: Joshua Brindle <method@manicmethod.com>
To: Vikram Noel Ambrose <noel.ambrose@gmail.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [PATCH][autotools] libselinux/load_policy.o compile error
Date: Thu, 04 Sep 2008 11:33:26 -0400 [thread overview]
Message-ID: <48BFFFC6.6090100@manicmethod.com> (raw)
In-Reply-To: <48BF58E7.4030806@gmail.com>
Vikram Noel Ambrose wrote:
> Here's the fix to that libselinux ld error you were getting.
>
Ok, applied and built fine. One interesting thing is that even without building the swig wrappers (--disable-swig) it still installs lib/python2.5/site-packages/selinux, which obviously wouldn't work without the accompanying .so file.
Also, it looks like any library that installs to /lib will also put their python stuff in /lib/python2.5. I don't know if python even knows to look there, and even if it does there is really no reason to put them there. libselinux.so and libsepol.so will need to go to /lib but the python stuff should go to /usr/lib and I don't see a different argument for the python stuff (only --libdir).
--
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:[~2008-09-04 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 3:41 [PATCH][autotools] libselinux/load_policy.o compile error Vikram Noel Ambrose
2008-09-04 15:33 ` Joshua Brindle [this message]
2008-09-04 16:51 ` Vikram Noel Ambrose
2008-09-04 18:09 ` Joshua Brindle
2008-09-15 21:15 ` Joshua Brindle
2008-09-26 1:09 ` Vikram Noel Ambrose
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=48BFFFC6.6090100@manicmethod.com \
--to=method@manicmethod.com \
--cc=noel.ambrose@gmail.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.