From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PATCH v4 01/10] ldconfig.8: Drop discussion of libc4,5 support.
Date: Sat, 7 Jan 2023 03:54:13 -0600 [thread overview]
Message-ID: <20230107095413.iz7jsiynquonpsvi@illithid> (raw)
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
Drop multiple paragraphs discussing libc4 and libc5 shared library
support. It was removed upstream in July; annotate commit.
---
man8/ldconfig.8 | 37 +++----------------------------------
1 file changed, 3 insertions(+), 34 deletions(-)
diff --git a/man8/ldconfig.8 b/man8/ldconfig.8
index de2b7a5c3..36b891dab 100644
--- a/man8/ldconfig.8
+++ b/man8/ldconfig.8
@@ -57,40 +57,9 @@ or
.B \%ldconfig
checks the header and filenames of the libraries it encounters when
determining which versions should have their links updated.
-.PP
-.B \%ldconfig
-will attempt to deduce the type of ELF libraries
-(i.e.,
-libc5 or libc6/glibc)
-based on what C libraries,
-if any,
-the library was linked against.
-.\" The following sentence looks suspect
-.\" (perhaps historical cruft) -- MTK, Jul 2005
-.\" Therefore, when making dynamic libraries,
-.\" it is wise to explicitly link against libc (use \-lc).
-.PP
-Some existing libraries do not contain enough information
-to allow the deduction of their type.
-Therefore,
-the
-.I /etc/ld.so.conf
-file format allows the specification of an expected type.
-This is used
-.I only
-for those ELF libraries which we can not work out.
-The format
-is "dirname=TYPE",
-where TYPE can be libc4,
-libc5,
-or libc6.
-(This syntax also works on the command line.)
-Spaces are
-.I not
-allowed.
-Also see the
-.B \-p
-option.
+.\" Support for libc4 and libc5 dropped in
+.\" 8ee878592c4a642937152c8308b8faef86bcfc40 (2022-07-14) as "obsolete
+.\" for over twenty years".
.B \%ldconfig
should normally be run by the superuser as it may require write
permission on some root owned directories and files.
--
2.30.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-01-07 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 9:54 G. Branden Robinson [this message]
2023-01-07 12:06 ` [PATCH v4 01/10] ldconfig.8: Drop discussion of libc4,5 support Alejandro Colomar
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=20230107095413.iz7jsiynquonpsvi@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx.manpages@gmail.com \
--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