All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: selinux@tycho.nsa.gov, Raphael Geissert <geissert@debian.org>,
	549610-forwarded@bugs.debian.org
Subject: Re: /lib/libsemanage.so.1 links to  /usr/lib/libustr-1.0.so.1
Date: Fri, 27 Nov 2009 13:03:40 -0500	[thread overview]
Message-ID: <4B10147C.7090801@manicmethod.com> (raw)
In-Reply-To: <4AD489A5.7010708@manicmethod.com>

Joshua Brindle wrote:
> Manoj Srivastava wrote:
>> Hi,
>>
>> As demonstrated by
>>
>> $ ldd /lib/libsemanage.so.1
>> linux-gate.so.1 => (0xb8092000)
>> libsepol.so.1 => /lib/libsepol.so.1 (0xb8015000)
>> libselinux.so.1 => /lib/libselinux.so.1 (0xb7ffa000)
>> libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb7fe9000)
>> libustr-1.0.so.1 => /usr/lib/libustr-1.0.so.1 (0xb7fbf000)
>> libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7e60000)
>> libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7e5c000)
>> /lib/ld-linux.so.2 (0xb8093000)
>>
>> libsemanage1 links to libustr which is located under the,
>> possible separate or external, /usr partition, which would render
>> libsemanage unusable in such setups. (This dependency has been around
>> since 2.0.9).
>>
>> Should we move libsemanage1 to /usr/lib? The only reason for it
>> to be in /lib would be for early boot, where /usr might not be
>> available, but at this point, it is likely not usable without /usr
>> anyway.
>>
>> manoj
>
>
> Yes, I'm not sure why you'd need libsemanage during early boot, we
> probably should apply this:
>
> diff --git a/libsemanage/src/Makefile b/libsemanage/src/Makefile
> index cfb9558..c531a2f 100644
> --- a/libsemanage/src/Makefile
> +++ b/libsemanage/src/Makefile
> @@ -1,7 +1,7 @@
> # Installation directories.
> PREFIX ?= $(DESTDIR)/usr
> LIBDIR ?= $(PREFIX)/lib
> -SHLIBDIR ?= $(DESTDIR)/lib
> +SHLIBDIR ?= $(PREFIX)/lib
> INCLUDEDIR ?= $(PREFIX)/include
> PYLIBVER ?= $(shell python -c 'import sys;print "python%d.%d" %
> sys.version_info[0:2]')
> PYINC ?= /usr/include/${PYLIBVER}
>

Looks like I missed the libsemanage.so.1 libsemanage.so symlink, applied 
the following patch to libsemanage 2.0.43:

diff --git a/libsemanage/src/Makefile b/libsemanage/src/Makefile
index a249f0f..67afc60 100644
--- a/libsemanage/src/Makefile
+++ b/libsemanage/src/Makefile
@@ -1,7 +1,7 @@
  # Installation directories.
  PREFIX ?= $(DESTDIR)/usr
  LIBDIR ?= $(PREFIX)/lib
-SHLIBDIR ?= $(DESTDIR)/lib
+SHLIBDIR ?= $(PREFIX)/lib
  INCLUDEDIR ?= $(PREFIX)/include
  PYLIBVER ?= $(shell python -c 'import sys;print "python%d.%d" % 
sys.version_info[0:2]')
  PYINC ?= /usr/include/${PYLIBVER}
@@ -127,7 +127,7 @@ install: all
         test -d $(LIBDIR)/pkgconfig || install -m 755 -d 
$(LIBDIR)/pkgconfig
         install -m 644 $(LIBPC) $(LIBDIR)/pkgconfig
         test -f $(DEFAULT_SEMANAGE_CONF_LOCATION) || install -m 644 -D 
semanage.conf $(DEFAULT_SEMANAGE_CONF_LOCATION)
-       cd $(LIBDIR) && ln -sf ../../`basename $(SHLIBDIR)`/$(LIBSO) 
$(TARGET)
+       cd $(LIBDIR) && ln -sf $(LIBSO) $(TARGET)

  install-pywrap: pywrap
         test -d $(PYLIBDIR)/site-packages || install -m 755 -d 
$(PYLIBDIR)/site-packages

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

      parent reply	other threads:[~2009-11-27 18:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13  7:20 /lib/libsemanage.so.1 links to /usr/lib/libustr-1.0.so.1 Manoj Srivastava
2009-10-13 14:07 ` Joshua Brindle
2009-10-14  5:49   ` Manoj Srivastava
2009-10-19 14:20     ` Stephen Smalley
2009-10-19 15:07       ` Daniel J Walsh
2009-10-19 15:11         ` Stephen Smalley
2009-10-19 15:35           ` Daniel J Walsh
2009-10-19 19:10             ` Joshua Brindle
2009-10-21 14:03       ` Manoj Srivastava
2009-10-21 14:29         ` Stephen Smalley
2009-11-27 18:03   ` Joshua Brindle [this message]

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=4B10147C.7090801@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=549610-forwarded@bugs.debian.org \
    --cc=geissert@debian.org \
    --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.