From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject:
 Re: ldconfig messages - "path given more than once" + "can't stat file..."
Date: Thu, 14 May 2020 01:18:41 +0200
Message-ID: <2b94603a-d0ef-6744-7324-8c00bd43dcfd@ipfire.org>
In-Reply-To: <a834cb49-4897-d0b2-295e-b6cb322f5e71@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2471008351226916868=="
List-Id: <development.lists.ipfire.org>

--===============2471008351226916868==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

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
> 


--===============2471008351226916868==--