From: Diyab <diyab@diyab.net>
To: Colin Walters <walters@verbum.org>
Cc: max barwell <maxb@paradise.net.nz>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: libselinux.so: cannot open shared object file
Date: Thu, 04 Sep 2003 17:00:42 -0400 [thread overview]
Message-ID: <3F57A7FA.8050806@diyab.net> (raw)
In-Reply-To: <1062690102.15712.16.camel@columbia>
Colin Walters wrote:
> On Wed, 2003-09-03 at 20:59, max barwell wrote:
>
>>I am using debian sid, I compiled a 2.6.0-test4 kernel ready for use,
>>and downloaded Colin Walters SElinux packages, during their install, and
>>I'm not sure when as I wasn't watching, the install borked, and now when
>>I try to do anything ie type ls, I get the error message
>>
>>error while loading shared libraries: libselinux.so: cannot open shared
>>object file: No such file or directory
>
>
> Hm, for some reason the binaries are getting linked against
> libselinux.so instead of libselinux.so.1. I'll investigate this. In
> the meantime it should be sufficient to install libselinux1-dev.
>
>
> --
> 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.
>
> .
>
Why not just link libselinux.so to libselinux.so.1 ? That would at
least temporarily fix the problem would it not?
Timothy,
--
I put instant coffee in a microwave and almost went back in time.
-- Steven Wright
--
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:[~2003-09-04 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 0:59 libselinux.so: cannot open shared object file max barwell
2003-09-04 4:53 ` Russell Coker
2003-09-04 15:41 ` Colin Walters
2003-09-04 21:00 ` Diyab [this message]
2003-09-05 0:32 ` Brian May
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=3F57A7FA.8050806@diyab.net \
--to=diyab@diyab.net \
--cc=SELinux@tycho.nsa.gov \
--cc=maxb@paradise.net.nz \
--cc=walters@verbum.org \
/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.