From: Jorge Almeida <jjalmeida@gmail.com>
To: musl@lists.openwall.com
Subject: Re: getrandom()
Date: Thu, 28 Sep 2017 23:28:34 +0100 [thread overview]
Message-ID: <CAKpSnpLkd7OgZqc5xvJGvZ7rdnbp0zbpYSNuc1r8dhUtYdEMwQ@mail.gmail.com> (raw)
In-Reply-To: <20170928222024.GJ15263@port70.net>
On Thu, Sep 28, 2017 at 11:20 PM, Szabolcs Nagy <nsz@port70.net> wrote:
> * Jorge Almeida <jjalmeida@gmail.com> [2017-09-28 22:35:56 +0100]:
>> Will it be supported?
>> I heve the include/linux directory, installed from the kernel source
>> (4.13.2), and the random.h file exists, but it doesn't contain the
>> prototype for getrandom(). What to do?
>
> yes, musl can add it now that glibc decided on the api,
Great. Thanks
prev parent reply other threads:[~2017-09-28 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 21:35 getrandom() Jorge Almeida
2017-09-28 22:20 ` getrandom() Szabolcs Nagy
2017-09-28 22:28 ` Jorge Almeida [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=CAKpSnpLkd7OgZqc5xvJGvZ7rdnbp0zbpYSNuc1r8dhUtYdEMwQ@mail.gmail.com \
--to=jjalmeida@gmail.com \
--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).