From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@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 12:38:48 +0100
Message-ID: <441C681F-478D-43A4-8F15-849C29683399@ipfire.org>
In-Reply-To: <ebf05d56-7565-eb4d-14d0-3a2d5ef79194@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2289981932216769605=="
List-Id: <development.lists.ipfire.org>

--===============2289981932216769605==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Oh, yes, they show up with -v. But I wouldn=E2=80=99t worry about them...

> On 14 May 2020, at 12:36, Matthias Fischer <matthias.fischer(a)ipfire.org> =
wrote:
>=20
> Hi,
>=20
> 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).
>=20
> Install went ok.
>=20
> I restored my (main) backup - OK.
>=20
> Installed addons through pakfire - OK.
>=20
> Restored addon backups - OK.
>=20
> I upgraded some other programs (tmux / monit / privoxy / vnstat / squid
> graphs), which were compiled on the new 64bit devel.
>=20
> ["Devel64" =3D 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]
>=20
> All in all: no seen problems, everything is running.
>=20
> Then I compiled and installed an update for 'knot' (2.9.4).
>=20
> Just to be careful, I manually ran 'ldconfig -v' after upgrading.
>=20
> 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.
>=20
> 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.
>=20
> And yes, I was a bit stunned, too.
>=20
> Best,
> Matthias
>=20
> On 14.05.2020 12:38, Michael Tremer wrote:
>> Hi,
>>=20
>> I am confused now and cannot reproduce this on any of my systems.
>>=20
>> Where did this happen?
>>=20
>> -Michael
>>=20
>>> On 14 May 2020, at 08:54, Matthias Fischer <matthias.fischer(a)ipfire.org=
> wrote:
>>>=20
>>> =3D> Patched
>>>=20
>>> =3D> Works
>>>=20
>>> =3D> Messages about paths "given more than once" and "No such file or
>>> directory" are gone.
>>>=20
>>> 'ldconfig' is working 'without seen problems' on Core 144 / x86_64.
>>>=20
>>> Patch wanted? ;-)
>>>=20
>>> On 14.05.2020 01:40, Matthias Fischer wrote:
>>>> According to the discussion in the link cited below I built an attached
>>>> patch.
>>>>=20
>>>> Would this work?
>>>>=20
>>>> On 14.05.2020 01:18, Matthias Fischer wrote:
>>>>> In the meantime I've found this discussion:
>>>>>=20
>>>>> https://trac.clfs.org/ticket/1098
>>>>>=20
>>>>> Could it be that this behaviour is triggered by 'glibc'!?
>>>>>=20
>>>>> On 14.05.2020 00:38, Matthias Fischer wrote:
>>>>>> Hi,
>>>>>>=20
>>>>>> on a fresh Core 144 / x86_64 install, running without any seen problem=
s,
>>>>>> I get these "messages":
>>>>>>=20
>>>>>> ...
>>>>>> 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
>>>>>> ...
>>>>>>=20
>>>>>> when I run 'ldconfig -v'.
>>>>>>=20
>>>>>> This is new to me - I'm searching, but haven't found the reason yet. A=
nd
>>>>>> I'd like to know...
>>>>>>=20
>>>>>> Any ideas?
>>>>>>=20
>>>>>> Thanks in advance!
>>>>>>=20
>>>>>> Best,
>>>>>>=20
>>>>>> Matthias
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20


--===============2289981932216769605==--