New BIND releases ... 9.16.4: build, 'fatal error: lmdb.h: No such file or directory'

Ondřej Surý ondrej at
Thu Jun 18 05:47:43 UTC 2020

Did you came to get help or to argue?

LMDB support in BIND 9 comes with pkg-config support too, you can use and adjust the .pc file from any Linux distribution package.

It’s really not our fault the LMDB upstream decided to make it hard to use the library.

Ondřej Surý — ISC

> On 18 Jun 2020, at 07:15, PGNet Dev < at> wrote:
> On 6/17/20 9:48 PM, Ondřej Surý wrote:
>> Virtually everybody except upstream has modified LMDB to follow a normal directory layout and BIND expect that.
>> You should just move the header files and library to /usr/local/include and /usr/local/lib respectively.
> That's just a silly statement.
> 1st, /usr/local/lib is NOT a 'normal directory' layout for a number of distros -- /usr/local/lib64 is.  That assumption in bind's code is just wrong.
> Software should link against the libs, and include the headers, you TELL it to -- not what it arbitrarily 'expects'.
> Finally, if that's BIND's 'expectation', why does bind even have a =path config option for it?
> What's the basis for arbitrary choice of bind using pkg-config for some pkgs, providing well-functioning _CFLAGS/_LDFLAGS/_LIBS overrides for others -- but in the case of lmdb, neither -- just an 'expectation'?

More information about the bind-users mailing list