From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 214163] New: hardcoded library paths in FILES section
Date: Tue, 24 Aug 2021 10:06:55 +0000 [thread overview]
Message-ID: <bug-214163-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214163
Bug ID: 214163
Summary: hardcoded library paths in FILES section
Product: Documentation
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: giecrilj@stegny.2a.pl
Regression: No
For example:
/usr/lib/gconv Usual default gconv module path.
This is not the default path for 64-bit native programs under openSUSE. The
default path is:
* /usr/lib64/gconv for 64-bit native programs
* /usr/lib/gconv for 32-bit native programs
Therefore, it is not practical to patch the manual pages to replace lib with
lib64, for example.
Manual pages should support multiple architectures as a 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.
next reply other threads:[~2021-08-24 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 10:06 bugzilla-daemon [this message]
2021-08-24 21:40 ` [Bug 214163] hardcoded library paths in FILES section bugzilla-daemon
2021-08-25 21:59 ` bugzilla-daemon
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@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