All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] bind: build with threads and update configure options
Date: Mon, 20 Nov 2017 14:56:53 +0800	[thread overview]
Message-ID: <c6cfdf1e-010a-0257-b1f9-465159db5a1d@windriver.com> (raw)
In-Reply-To: <9dabcc17-148f-a0d9-d9d6-3abcd2836ea0@windriver.com>

On 2017年11月17日 09:46, Kang Kai wrote:
> On 2017年11月16日 18:27, Andre McCurdy wrote:
>> On Fri, May 26, 2017 at 8:24 PM, Kang Kai <Kai.Kang@windriver.com> 
>> wrote:
>>> On 2017年05月23日 17:58, Kang Kai wrote:
>>> On 2017年05月19日 19:47, Burton, Ross wrote:
>>> On 19 May 2017 at 09:52, <kai.kang@windriver.com> wrote:
>>>> 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.
>> It seems this change was made without taking into account the advice 
>> given in:
>>
>> http://git.openembedded.org/openembedded-core/commit/?id=f28757a4b89447ea528cba987f0396b92aa0bbfe
>>
>> "If and when we ship bind's shared libraries we should ensure that the
>> libraries go into a separate package."

Libraries are packaged to bind-libs which has been created by :

http://git.openembedded.org/openembedded-core/commit/?id=d74ebc91388941295a2321a295cdb06ee87fc38b


Regards,
Kai

>>
>> In rocko builds I see "named" running on port 53 and dnsmasq fails to 
>> start...
>
> Thanks. I'll check that.
>
> --Kai
>
>>
>>>> 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.
>>>>
>>>> Update file/directory ownerships to fix daemon start failure.
>
>

-- 
Regards,
Neil | Kai Kang



  reply	other threads:[~2017-11-20  6:57 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 [this message]
2017-11-21  3:27               ` Andre McCurdy
2017-11-16 11:50   ` André Draszik
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=c6cfdf1e-010a-0257-b1f9-465159db5a1d@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=armccurdy@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.