From: grunpferd at netscape.net <grunpferd@netscape.net>
To: buildroot@busybox.net
Subject: [Buildroot] Failing bind 9.11.1-P3 configure failure
Date: Tue, 8 Aug 2017 19:29:56 -0400 [thread overview]
Message-ID: <15dc42eeceb-3056-92bf@webprd-m104.mail.aol.com> (raw)
In-Reply-To: <20170808190750.21fad1a3@gmx.net>
G'day Peter,
>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...
No problems, rather get the issue sorted while still in -rc1.
I guess the problem with random configurations is they are not "real" or "real" enough!
>>
>>
>> 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...
Bind might run a little slower but at least it builds and works.
I think bind used to use BSD db and has since shifted to mdb.
The more serious issue is that configure is using local files and failing in this cross compilation toolchain generated by buildroot.
While the patch works in terms of allowing buildroot to build bind there is a deeper problem here.
The problem is more in the configuration tools getting it wrong, why is it looking at local header files at all, rather than the buildroot generated header files!
Keep the good work coming,
Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170808/53adc3e1/attachment.html>
next prev parent reply other threads:[~2017-08-08 23:29 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
2017-08-08 23:29 ` grunpferd at netscape.net [this message]
-- 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=15dc42eeceb-3056-92bf@webprd-m104.mail.aol.com \
--to=grunpferd@netscape.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