All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Openembedded-core@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Cc: tmark@isc.org, Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>,
	Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: Re: [OE-core] [PATCH] dhcp: use included bind version
Date: Fri, 12 Jun 2020 17:41:36 -0700	[thread overview]
Message-ID: <14618585.ZI4Hmrvx6b@tyche> (raw)
In-Reply-To: <b10c95a7-5d8b-d922-ad40-6d97cceb9c85@gmail.com>

On Wednesday, June 10, 2020 9:36:52 AM PDT Vyacheslav Yurkov wrote:
> On 10.06.2020 17:05, Richard Purdie wrote:
> > You seem to disable parallel make yet no mention of that in the log?
> 
> Right, I forgot to mention that in the commit message. Building bind at
> 'compile' stage breaks parallel make. I assume that can be addressed,
> but I'd need to take a look at how to set that dependency with autotools.
> 
> > Why doesn't dhcp build and link against a static libbind by default if
> > these issues are present the the dhcp authors don't want to work with
> > such libbinds?
> 
> That's a good question. I assume the alternative is disable threads in
> bind recipes then a shared library can be used by both, dhcp and named
> (DNS). Hopefully Thomas from ISC (in CC) could clarify this better than me.
> 

I think it would be good to share if we can. Shipping two versions of bind 
libraries is less than ideal, have you explored disabling threading in the 
bind recipe and see if named is happy with that ?

> > Cheers,
> > 
> > Richard
> 
> Regards,
> Vyacheslav





  reply	other threads:[~2020-06-13  0:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 14:35 [PATCH] dhcp: use included bind version Vyacheslav Yurkov
2020-06-10 15:02 ` ✗ patchtest: failure for " Patchwork
2020-06-10 15:05 ` [OE-core] [PATCH] " Richard Purdie
2020-06-10 16:36   ` Vyacheslav Yurkov
2020-06-13  0:41     ` Khem Raj [this message]
2020-06-13  8:31       ` Vyacheslav Yurkov
2020-06-17 10:35         ` Alexander Kanavin
2020-06-10 16:07 ` Adrian Bunk
2020-06-10 16:31   ` Vyacheslav Yurkov
2020-06-10 17:42     ` Adrian Bunk
2020-06-10 18:40       ` Vyacheslav Yurkov

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=14618585.ZI4Hmrvx6b@tyche \
    --to=raj.khem@gmail.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=Vyacheslav.Yurkov@bruker.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=tmark@isc.org \
    --cc=uvv.mail@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 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.