Hello Maurice!

08 Feb 2018 14:47, Maurice Kinal wrote to Benny Pedersen:

 MK> From my observations glibc-2.27 is the greater culprit.

gentoo devs agre with you

 MK> My current 
 MK> 'stable' system is booting a linux-4.15.1 kernel but with glibc-2.26 
 MK> as shown below;

i have only 2.25, i dont think kernel changes userland problems, so here i just
stay safe on kernel versions for a while, i have to make tarballs soon to get
new harddisk installed, not fun

 MK> ----- ':read !uname -a' starts
 MK> Linux mikey 4.15.1 #1 SMP Sun Feb 4 11:04:33 UTC 2018 x86_64 Intel(R) 
 MK> Atom(TM) CPU C2758 @ 2.40GHz GenuineIntel GNU/Linux
 MK> ----- ':read !uname -a' ends

should i say wish it was mine ? :)

 MK> ----- ':read !/lib/libc.so.6' starts
 MK> GNU C Library (GNU libc) stable release version 2.26, by Roland 
 MK> Compiled by GNU CC version 7.3.0.
 MK> Available extensions:
 MK>         crypt add-on version 2.1 by Michael Glad and others
 MK>         GNU Libidn by Simon Josefsson
 MK>         Native POSIX Threads Library by Ulrich Drepper et al
 MK>         BIND-8.2.3-T5B

bind8 still in use ?

 MK> libc ABIs: UNIQUE IFUNC

dont know much here

 MK> ----- ':read !/lib/libc.so.6' ends

 MK> Both of the above play nicely with libelf-0.170.so which is not the 
 MK> case with glibc-2.27 and linux-4.15.1.  Also I noticed some linker 
 MK> issues with libjpeg since we last chatted.  Bottomline is that I am 
 MK> obviously not ready for a glibc-2.27 'upgrade'.

do you like to try elfutils ?, that make libelf unneded on gentoo here


 Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.9.76-gentoo-r1 (i686))