From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] bind: build with threads and update configure options
Date: Thu, 16 Nov 2017 11:50:29 +0000 [thread overview]
Message-ID: <1510833029.4049.77.camel@andred.net> (raw)
In-Reply-To: <d0db7f059097d0271e5808dda280140ef49aae6f.1495183828.git.kai.kang@windriver.com>
On Fri, 2017-05-19 at 16:52 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> Build without threads for bind is inherited from legacy openembedded.
> All libc's support proper threading on Linux now, so enable threads
> support for bind.
>
> It is also need to disable static library build which cause package dhcp
> fail to build after enable bind threads support.
>
> Options devpoll and epoll are configured to choose most preferable
> multiplex method for unix socket. The priorities are: epoll > poll >
> select. When set '--enable-epoll', it just defines a var and include
> header file that is available for cross compile. So use epoll for bind.
>
> Add PACKAGECONFIG 'urandom' that could use /dev/urandom as random device.
I'd say using /dev/urandom should also be made the default.
Cheers,
Andre'
next prev parent reply other threads:[~2017-11-16 11:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 8:52 [PATCH 0/2] Build bind with threads kai.kang
2017-05-19 8:52 ` [PATCH 1/2] bind: build with threads and update configure options kai.kang
2017-05-19 11:47 ` Burton, Ross
2017-05-23 9:58 ` Kang Kai
2017-05-27 3:24 ` Kang Kai
2017-11-16 10:27 ` Andre McCurdy
2017-11-17 1:46 ` Kang Kai
2017-11-20 6:56 ` Kang Kai
2017-11-21 3:27 ` Andre McCurdy
2017-11-16 11:50 ` André Draszik [this message]
2017-05-19 8:52 ` [PATCH 2/2] dhcp: build shared libraries kai.kang
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=1510833029.4049.77.camel@andred.net \
--to=git@andred.net \
--cc=openembedded-core@lists.openembedded.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