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 09:54:13 +0200 [thread overview]
Message-ID: <c2d2a0c6-0c3b-24bd-47d4-dcec1799c36c@ipfire.org> (raw)
In-Reply-To: <edb1dd90-28fc-b019-da35-3acb88699ff3@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
=> 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
>>>
>>
>
next prev parent reply other threads:[~2020-05-14 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 22:38 Matthias Fischer
2020-05-13 23:18 ` Matthias Fischer
2020-05-13 23:40 ` Matthias Fischer
2020-05-14 7:54 ` Matthias Fischer [this message]
2020-05-14 10:38 ` Michael Tremer
2020-05-14 11:36 ` Matthias Fischer
2020-05-14 11:38 ` Michael Tremer
2020-05-14 12:01 ` Matthias Fischer
2020-05-14 12:09 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2d2a0c6-0c3b-24bd-47d4-dcec1799c36c@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox