From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: ACCT_VERSION: linux vs musl
Date: Thu, 9 Mar 2017 23:30:12 +0100 [thread overview]
Message-ID: <20170309223012.GK2082@port70.net> (raw)
In-Reply-To: <CAPLrYERdwdy=8x54XczuPpdB1zkVyPC5ev6ifsS+hW8MwF_Mqg@mail.gmail.com>
* Daniel Cegiełka <daniel.cegielka@gmail.com> [2017-03-09 22:38:55 +0100]:
> linux:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/acct.h?id=refs/tags/v4.11-rc1
>
> old 3.2 kernel:
>
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/include/linux/acct.h?id=refs/tags/v3.2.86
>
>
> and musl:
>
> http://git.musl-libc.org/cgit/musl/tree/include/sys/acct.h
sys/acct.h never exposed ACCT_VERSION
(may be an oversight in glibc)
so user code cannot rely on it.
prev parent reply other threads:[~2017-03-09 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 21:38 Daniel Cegiełka
2017-03-09 22:30 ` Szabolcs Nagy [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=20170309223012.GK2082@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).