On Wed, Feb 26, 2014 at 10:22 PM, Daniel J Walsh <dwa...@redhat.com> wrote: > On 02/26/2014 03:05 PM, Zbigniew Jędrzejewski-Szmek wrote: >> On Wed, Feb 26, 2014 at 08:54:34PM +0100, Thomas H.P. Andersen wrote: >>> The todo says: "something pulls in pcre as shared object dependency into >>> our daemons such as hostnamed" >>> >>> Normal buiild: ldd ./systemd-hostnamed linux-vdso.so.1 => >>> (0x00007fff247bc000) libselinux.so.1 => /lib64/libselinux.so.1 >>> (0x00007f7ec47f7000) librt.so.1 => /lib64/librt.so.1 >>> (0x00007f7ec45ef000) libdl.so.2 => /lib64/libdl.so.2 >>> (0x00007f7ec43ea000) libpthread.so.0 => /lib64/libpthread.so.0 >>> (0x00007f7ec41cd000) libc.so.6 => /lib64/libc.so.6 (0x00007f7ec3e0e000) >>> /lib64/ld-linux-x86-64.so.2 (0x00007f7ec4a2f000) libpcre.so.1 => >>> /lib64/libpcre.so.1 (0x00007f7ec3ba7000) liblzma.so.5 => >>> /lib64/liblzma.so.5 (0x00007f7ec3982000) >> It's a selinux problem (or not, if it actually uses pcre's). ldd >> /lib64/libselinux.so.1 linux-vdso.so.1 => (0x00007fff58bfe000) >> libpcre.so.1 => /lib64/libpcre.so.1 (0x0000003803400000) liblzma.so.5 => >> /lib64/liblzma.so.5 (0x00000035d6800000) libdl.so.2 => /lib64/libdl.so.2 >> (0x00000035d2c00000) libc.so.6 => /lib64/libc.so.6 (0x00000035d2000000) >> /lib64/ld-linux-x86-64.so.2 (0x00000035d1800000) libpthread.so.0 => >> /lib64/libpthread.so.0 (0x00000035d2800000)
> libselinux and systemd take advantage of pcre for speeding up the handling of > reading in the labeling file. Well, it's the crazy _init constructor that libselinux needs that pulls that in as a first-level dependency. People should just not use that insane stuff. Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
