From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: ldconfig messages - "path given more than once" + "can't stat file..." Date: Thu, 14 May 2020 09:54:13 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4282198144931314609==" List-Id: --===============4282198144931314609== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit => 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 >>> >> > --===============4282198144931314609==--