Hi, first, I installed Core 144 / 64bit, built on a new 64bit Devel machine. I already integrated an upgrade in this install (squid 4.11 with latest patch). Install went ok. I restored my (main) backup - OK. Installed addons through pakfire - OK. Restored addon backups - OK. I upgraded some other programs (tmux / monit / privoxy / vnstat / squid graphs), which were compiled on the new 64bit devel. ["Devel64" = Linux Devel64 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux, running Ubuntu 18.04.4 LTS] All in all: no seen problems, everything is running. Then I compiled and installed an update for 'knot' (2.9.4). Just to be careful, I manually ran 'ldconfig -v' after upgrading. And then I suddenly saw these messages the first time. With the new 'glibc' patch they're gone now - and the lib list is exactly the same. As I see it, the whole system is running without any problems. Only 'ldconfig' did complain and then I started to search for the reason. And yes, I was a bit stunned, too. Best, Matthias On 14.05.2020 12:38, Michael Tremer wrote: > Hi, > > I am confused now and cannot reproduce this on any of my systems. > > Where did this happen? > > -Michael > >> On 14 May 2020, at 08:54, Matthias Fischer wrote: >> >> => Patched >> >> => Works >> >> => Messages about paths "given more than once" and "No such file or >> directory" are gone. >> >> 'ldconfig' is working 'without seen problems' on Core 144 / x86_64. >> >> Patch wanted? ;-) >> >> On 14.05.2020 01:40, Matthias Fischer wrote: >>> According to the discussion in the link cited below I built an attached >>> patch. >>> >>> Would this work? >>> >>> On 14.05.2020 01:18, Matthias Fischer wrote: >>>> In the meantime I've found this discussion: >>>> >>>> https://trac.clfs.org/ticket/1098 >>>> >>>> Could it be that this behaviour is triggered by 'glibc'!? >>>> >>>> On 14.05.2020 00:38, Matthias Fischer wrote: >>>>> Hi, >>>>> >>>>> on a fresh Core 144 / x86_64 install, running without any seen problems, >>>>> I get these "messages": >>>>> >>>>> ... >>>>> ldconfig: Path `/lib64' given more than once >>>>> ldconfig: Can't stat /libx32: No such file or directory >>>>> ldconfig: Path `/usr/lib64' given more than once >>>>> ldconfig: Can't stat /usr/libx32: No such file or directory >>>>> ... >>>>> >>>>> when I run 'ldconfig -v'. >>>>> >>>>> This is new to me - I'm searching, but haven't found the reason yet. And >>>>> I'd like to know... >>>>> >>>>> Any ideas? >>>>> >>>>> Thanks in advance! >>>>> >>>>> Best, >>>>> >>>>> Matthias >>>>> >>>> >>> >> >