From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 217291] librt empty, man pages should not tell users to link with -lrt
Date: Wed, 05 Apr 2023 05:02:30 +0000 [thread overview]
Message-ID: <bug-217291-11311-673JRNs521@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217291-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217291
--- Comment #2 from Janne Blomqvist (blomqvist.janne@gmail.com) ---
(In reply to Sam James from comment #1)
> It depends on one's libc (non-glibc implementations are free to need it
> still) rather than being obsolete altogether.
>
> Ultimately, a configure test is needed.
I'm not sure the man-pages project really concerns itself with non-glibc
libc's. Of course you're right that a project that wants to be portable to
multiple libc's will need configure tests (or equivalent). But that doesn't
mean that a project that aims to document how to use glibc shouldn't tell users
how to use it.
My suggestion is that the man pages I mentioned above should have languages
like clock_gettime and friends already have. That is, from
https://www.man7.org/linux/man-pages/man3/clock_gettime.3.html :
Link with -lrt (only for glibc versions before 2.17).
Or in the current repo:
.SH LIBRARY
Standard C library
.RI ( libc ", " \-lc ),
since glibc 2.17
.PP
Before glibc 2.17,
Real-time library
.RI ( librt ", " \-lrt )
(Not sure why one needs to explicitly tell to link with libc (-lc) and thus how
this is an improvement over the older version published on the web page (and in
most Linux distros man pages), but I digress)
--
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 prev parent reply other threads:[~2023-04-05 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 8:23 [Bug 217291] New: librt empty, man pages should not tell users to link with -lrt bugzilla-daemon
2023-04-05 0:52 ` [Bug 217291] " bugzilla-daemon
2023-04-05 5:02 ` bugzilla-daemon [this message]
2023-04-07 23:28 ` 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-217291-11311-673JRNs521@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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