Re: baffled by a slightly broken systemd and /lib/systemd/libsystemd-shared-235.so

[Dennis Clarke <dc@oetec.com>]

On 28/03/18 03:26 PM, Dennis Clarke wrote:
> On 28/03/18 01:00 PM, John Paul Adrian Glaubitz wrote:
> > Hi Dennis!
> >
> > Have you tried dist-upgrading your system?
> >
> > I spotted systemd 235 and maybe the binary was built with a broken 
> > binutils version which can happen and cause weird crashes and 
> > corrupted binaries.

Fixed !

root@nix:~# ls -lap /lib/systemd/libsystemd-shared*
-rw-r--r-- 1 root root 2957232 Mar 20 22:22 
/lib/systemd/libsystemd-shared-238.so
root@nix:~# ldd /lib/systemd/libsystemd-shared-238.so
        linux-vdso64.so.1 (0x00007fffb2c60000)
        libpthread.so.0 => /lib/powerpc64-linux-gnu/libpthread.so.0 
(0x00007fffb2910000)
        libc.so.6 => /lib/powerpc64-linux-gnu/libc.so.6 
(0x00007fffb2700000)
        librt.so.1 => /lib/powerpc64-linux-gnu/librt.so.1 
(0x00007fffb26d0000)
        libcap.so.2 => /lib/powerpc64-linux-gnu/libcap.so.2 
(0x00007fffb26a0000)
        libacl.so.1 => /lib/powerpc64-linux-gnu/libacl.so.1 
(0x00007fffb2670000)
        libcryptsetup.so.12 => 
/lib/powerpc64-linux-gnu/libcryptsetup.so.12 (0x00007fffb25f0000)
        libgcrypt.so.20 => /lib/powerpc64-linux-gnu/libgcrypt.so.20 
(0x00007fffb24f0000)
        libip4tc.so.0 => /usr/lib/powerpc64-linux-gnu/libip4tc.so.0 
(0x00007fffb24c0000)
        libseccomp.so.2 => /lib/powerpc64-linux-gnu/libseccomp.so.2 
(0x00007fffb2450000)
        libselinux.so.1 => /lib/powerpc64-linux-gnu/libselinux.so.1 
(0x00007fffb23f0000)
        libidn.so.11 => /lib/powerpc64-linux-gnu/libidn.so.11 
(0x00007fffb2390000)
        liblzma.so.5 => /lib/powerpc64-linux-gnu/liblzma.so.5 
(0x00007fffb2340000)
        liblz4.so.1 => /usr/lib/powerpc64-linux-gnu/liblz4.so.1 
(0x00007fffb2300000)
        libblkid.so.1 => /lib/powerpc64-linux-gnu/libblkid.so.1 
(0x00007fffb2270000)
        libmount.so.1 => /lib/powerpc64-linux-gnu/libmount.so.1 
(0x00007fffb21e0000)
        /lib64/ld64.so.1 (0x00007fffb2c80000)
        libattr.so.1 => /lib/powerpc64-linux-gnu/libattr.so.1 
(0x00007fffb21b0000)
        libuuid.so.1 => /lib/powerpc64-linux-gnu/libuuid.so.1 
(0x00007fffb2180000)
        libdevmapper.so.1.02.1 => 
/lib/powerpc64-linux-gnu/libdevmapper.so.1.02.1 (0x00007fffb20d0000)
        libargon2.so.0 => /usr/lib/powerpc64-linux-gnu/libargon2.so.0 
(0x00007fffb20a0000)
        libdl.so.2 => /lib/powerpc64-linux-gnu/libdl.so.2 
(0x00007fffb2070000)
        libjson-c.so.3 => /lib/powerpc64-linux-gnu/libjson-c.so.3 
(0x00007fffb2040000)
        libgpg-error.so.0 => /lib/powerpc64-linux-gnu/libgpg-error.so.0 
(0x00007fffb1ff0000)
        libpcre.so.3 => /lib/powerpc64-linux-gnu/libpcre.so.3 
(0x00007fffb1f50000)
        libudev.so.1 => /lib/powerpc64-linux-gnu/libudev.so.1 
(0x00007fffb1f00000)
        libm.so.6 => /lib/powerpc64-linux-gnu/libm.so.6 
(0x00007fffb1e00000)
root@nix:~#

root@nix:~# cat /proc/version
Linux version 4.15.0-2-powerpc64 (debian-kernel@lists.debian.org) (gcc 
version 7.3.0 (Debian 7.3.0-11)) #1 SMP Debian 4.15.11-1 (2018-03-20)

I will use that same config and try a build of 4.15.14 with the binutils
that are in the system area and then try again with binutils in my
/usr/local also.  I'll let you know if smoke comes out.

Thank you Sir !

Dennis