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}
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
