[Buildroot] Package configure script environment

Paul C Diem PCDiem at FoxValley.net
Thu May 7 22:10:21 UTC 2020


I am using the one from buildroot. buildroot-2020.02.1 does not include 
unbound. I pulled the unbound package info from 
https://git.buildroot.net/buildroot/tree/package/unbound?h=75021e0ceb841d743390a9fceff8d0ae4f513db2 
and that fails on the configure script because it can't find ssl.h. Like 
I said, it seems to be looking in my system's /usr/include directory 
instead of the host sysroot directory.

On 5/7/2020 2:31 PM, Thomas Petazzoni wrote:
> Hello,
>
> On Thu, 7 May 2020 12:59:04 -0500
> Paul C Diem <PCDiem at FoxValley.net> wrote:
>
>> I'm trying to find how buildroot execute package configure scripts.
>> Specifically, I'm trying to build unbound. It build fine under buildroot
>> 2019.02 but I'm having trouble under 2020.02.1. The problem is that the
>> ubnound configure script looks for include files (such as ssl.h) in
>> directories such as /usr. It appears that from the configure script's
>> perspective, /usr is the the /usr of the system I'm building on. It
>> seems it should be the host /usr from sysroot. I assume a lot of
>> configure scripts look for the existence of files in include and
>> libraries directories and I would have thought buildroot chroot'ed into
>> the host filesystem root when it ran the package configure scripts. Can
>> someone explain in what environment the package configure scripts are
>> executed?
> Why don't you use the "unbound" package that Buildroot has in
> package/unbound/ ? It is already integrated, and therefore solves all
> those cross-compilation issues for you.
>
> Rule: if you're building something manually against Buildroot, you're
> most likely wrong. You should be using an existing package, or create
> your own package.
>
> Hope this helps!
>
> Thomas


More information about the buildroot mailing list