linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Puiu <stefan.puiu@gmail.com>
To: Eugene Syromyatnikov <evgsyr@gmail.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	lnx-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH 00/45] Add LIBRARY section (based on FreeBSD manual pages)
Date: Fri, 17 Sep 2021 11:12:49 +0300	[thread overview]
Message-ID: <CACKs7VB6BZ876rLs69e7h1McCBLp47bk7OR4+28PMGDOc84tuw@mail.gmail.com> (raw)
In-Reply-To: <CACGkJdt0Yg2i-R3dkuANSqKoDu0oCk7bz43tAP4dojTHeCL6Gg@mail.gmail.com>

Hi Eugene,

On Tue, Sep 14, 2021 at 11:30 AM Eugene Syromyatnikov <evgsyr@gmail.com> wrote:
>
> On Tue, Sep 14, 2021 at 2:53 AM Stefan Puiu <stefan.puiu@gmail.com> wrote:
[...]
> > Also, on FreeBSD it's quite obvious you're talking about THE library.
> > But on Linux, you have glibc, musl libc, diet libc... Is the plan to
> > document requirements for all of these? E.g link with -lm on musl
> > libc, no special flags on glibc..?
>
> I think, the split is codified in the standards[1][2][3][4][5] (so,
> -lm/-lrt are expected to be supported by the compiler, per my
> understanding, and providing the necessary -l* option will always

I think libc provides libm/librt as library files; the linker just
finds them in /usr/lib, /usr/lib64 or whatever other folder they are
installed into. So I would say it's not "supported by the compiler"
technically, but by libc.

> work, because it's codified in C standard, contrary to not providing
> one) and the fact that glibc provides libm/librt symbols in -lc is
> more akin to a bit of convenience (for application or glibc
> developers, not sure which ones), and not something one should rely
> upon.

That's assuming that the libraries adhere to those standards, I'm not
sure if that's the situation. There are also functions like backtrace
(https://man7.org/linux/man-pages/man3/backtrace.3.html) which are
extensions, and some might not be implemented in other libraries
besides glibc. Maybe the Linux man-pages should mention glibc
explicitly instead of a rather ambiguous libc? And then details about
the other libs can be added, wherever they differ.

Thanks,
Stefan.

>
> [1] https://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/libc.html
> [2] https://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/libm.html
> [3] https://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/libpthread.html
> [4] https://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/libdl.html
> [5] https://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/librt.html
>
> --
> Eugene Syromyatnikov
> mailto:evgsyr@gmail.com
> xmpp:esyr@jabber.{ru|org}

  parent reply	other threads:[~2021-09-17  8:13 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 16:00 [PATCH 00/45] Add LIBRARY section (based on FreeBSD manual pages) Alejandro Colomar
2021-09-11 16:00 ` [PATCH 01/45] _exit.2: Add LIBRARY section Alejandro Colomar
2021-09-11 16:00 ` [PATCH 02/45] keyctl.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 03/45] gamma.3: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 04/45] request_key.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 05/45] write.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 06/45] wait4.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 07/45] wait.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 08/45] vmsplice.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 09/45] vm86.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 10/45] vhangup.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 11/45] vfork.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 12/45] utimensat.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 13/45] utime.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 14/45] ustat.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 15/45] userfaultfd.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 16/45] unshare.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 17/45] uname.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 18/45] umount.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 19/45] tkill.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 21/45] unlink.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 22/45] umask.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 23/45] truncate.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 24/45] timer_getoverrun.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 25/45] timerfd_create.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 26/45] timer_delete.2: " Alejandro Colomar
2021-09-11 16:00 ` [PATCH 27/45] timer_create.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 28/45] time.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 29/45] tee.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 30/45] syslog.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 31/45] sysinfo.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 32/45] syscall.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 33/45] sync_file_range.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 34/45] sync.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 35/45] symlink.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 36/45] swapon.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 37/45] subpage_prot.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 38/45] statx.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 39/45] stat.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 40/45] spu_run.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 41/45] spu_create.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 42/45] splice.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 43/45] socketpair.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 44/45] socketcall.2: " Alejandro Colomar
2021-09-11 16:01 ` [PATCH 45/45] sigwaitinfo.2: " Alejandro Colomar
2021-09-11 18:29 ` [PATCH 00/45] Add LIBRARY section (based on FreeBSD manual pages) Eugene Syromyatnikov
2021-09-11 18:40   ` Alejandro Colomar (man-pages)
2021-09-11 22:24     ` Eugene Syromyatnikov
2021-09-11 22:37       ` Alejandro Colomar (man-pages)
2021-09-13 18:42 ` Stefan Puiu
2021-09-14  8:30   ` Eugene Syromyatnikov
2021-09-14  8:32     ` Eugene Syromyatnikov
2021-09-15 20:20     ` Alejandro Colomar (man-pages)
2021-09-17  8:12     ` Stefan Puiu [this message]
2021-09-17  8:21     ` Florian Weimer

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=CACKs7VB6BZ876rLs69e7h1McCBLp47bk7OR4+28PMGDOc84tuw@mail.gmail.com \
    --to=stefan.puiu@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=evgsyr@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).