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:07:50 +0200	[thread overview]
Message-ID: <20170808190750.21fad1a3@gmx.net> (raw)
In-Reply-To: <15dbf45f074-58b7-6223@webprd-a18.mail.aol.com>

Hello 'grunpferd',

On Mon, 7 Aug 2017 20:36:58 -0400, grunpferd at netscape.net wrote:

> 
> It looks like there is some confusion over the local existence of header files resulting in error during configure.
> 
> 
> 
> > Local build of bind here (with a random configuration) succeeds, mind to try
> > the following buildroot patch:
> I used the +       --without-lmdb \ option and that does work.

Thanks for testing...

> 
> 
> I guess the the real issue is why it is looking at local header files at all, rather than the buildroot headers.
> Also I presume why bind wants to try and use -lmdb is to speed up some object store and retrieval,
> so maybe the right solution is to build a local version of mdb and have host headers and library available for the target.

Yes this would be a nice buildroot feature, but I think there is no lmdb (Lightning
Memory-mapped Database) package yet in buildroot to use...

Regards,
Peter

> I have not tested the BR2_COMPILER_PARANOID_UNSAFE_PATH facility, prefer to let the build complete so I can test the resulting rootfs first!
> 
> 
> Ross
> 
> 

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

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

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=20170808190750.21fad1a3@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