From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 214163] hardcoded library paths in FILES section
Date: Wed, 25 Aug 2021 21:59:22 +0000 [thread overview]
Message-ID: <bug-214163-11311-0n2d5IIThW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214163-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214163
--- Comment #2 from Christopher Yeleighton (giecrilj@stegny.2a.pl) ---
This is the fix for SUSE. I believe Debian has a different multiarch fs
layout. But it can stay if the LFS says so.
In ldconfig(8) terms, we would probably take the subdirectory "gconv" of the
"trusted directory" for the active architecture under /usr. I would appreciate
a reference to that manual page containing the authoritative explanation of the
concept.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2021-08-25 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 10:06 [Bug 214163] New: hardcoded library paths in FILES section bugzilla-daemon
2021-08-24 21:40 ` [Bug 214163] " bugzilla-daemon
2021-08-25 21:59 ` bugzilla-daemon [this message]
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=bug-214163-11311-0n2d5IIThW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-man@vger.kernel.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