Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Failing bind 9.11.1-P3 configure failure
Date: Tue, 8 Aug 2017 19:00:23 +0200	[thread overview]
Message-ID: <20170808190023.2a1c6a6b@gmx.net> (raw)
In-Reply-To: <2de931b7-cef0-5eb4-07bf-55db96252451@mind.be>

Hello Arnout,

On Tue, 8 Aug 2017 16:18:35 +0200, Arnout Vandecappelle <arnout@mind.be> wrote:

>  Hi Peter,
> 
> On 08-08-17 00:19, Peter Seiderer wrote:
> > Local build of bind here (with a random configuration) succeeds, mind to try
> > the following buildroot patch:
> > 
> > diff --git a/package/bind/bind.mk b/package/bind/bind.mk
> > index 988f40e1c2..c65568e9e3 100644
> > --- a/package/bind/bind.mk
> > +++ b/package/bind/bind.mk
> > @@ -24,6 +24,7 @@ BIND_CONF_ENV = \
> >         BUILD_CC="$(TARGET_CC)" \
> >         BUILD_CFLAGS="$(TARGET_CFLAGS)"
> >  BIND_CONF_OPTS = \
> > +       --without-lmdb \
> >         --with-libjson=no \
> >         --with-randomdev=/dev/urandom \
> >         --enable-epoll \
> 
>  Could you send this as an official patch?

O.k, patch is on the way...

> 
> 
> > (*) Using a real name instead of any pseudonym or fake name is preferred
> 
>  Actually, only when submitting patches. For bug reporting, asking questions, on
> IRC, etc. use pseudonyms all you like.

And thanks for clarifying...

Regards,
Peter

> 
>  Regards,
>  Arnout
> 

  reply	other threads:[~2017-08-08 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07  1:53 [Buildroot] Failing bind 9.11.1-P3 configure failure grunpferd at netscape.net
2017-08-07 22:19 ` Peter Seiderer
2017-08-08 14:18   ` Arnout Vandecappelle
2017-08-08 17:00     ` Peter Seiderer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-08  0:36 grunpferd at netscape.net
2017-08-08 17:07 ` Peter Seiderer
2017-08-08 23:29   ` grunpferd at netscape.net

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=20170808190023.2a1c6a6b@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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