Description of problem: The configure script returns "Unknown Berkeley DB major version in db.h" for some reason. Nothing in this regard has changed in libdb recently, db.h from F21 and from rawhide are identical. Also, nothing has changed in openldap's configure since the last build (Jan 27, 2015: http://koji.fedoraproject.org/koji/buildinfo?buildID=606939). I suspect this to be some weirdness in the autoconf machinery, but I need to investigate this a bit more. Steps to Reproduce: 1. Try mockbuild (or regular build) of openldap for Fedora Rawhide Actual results: checking for db.h... yes checking for Berkeley DB major version in db.h... none configure: error: Unknown Berkeley DB major version in db.h Expected results: checking for db.h... yes checking for Berkeley DB major version in db.h... 5 checking for Berkeley DB minor version in db.h... 3
Pavel, does this look familiar? Have there been any changes recently in the autotools chain? I'm not even sure how to debug this...
Sorry for the delay, my IMAP reader was KO. Grepping says it is OL_BDB_HEADER_VERSION macro. Isn't this related to gcc update to 5.0.0? The check is done via 'cc -E conftest.c', conftest.c contains (something like): #include <db.h> #ifndef DB_VERSION_MAJOR # define DB_VERSION_MAJOR 1 #endif __db_version DB_VERSION_MAJOR Using cpp conftest.c with slightly modified lines: #include <db.h> __db_version (DB_VERSION_MAJOR) shows that new you can not simply grep for __db_version now, output: ) # 2 "conftest.c" __db_version ( # 2 "conftest.c" 3 4 5 # 2 "conftest.c" ) Pavel
Hmm, I didn't find anything related to this among the GCC 5 changes. Running cpp with the -P option seems to fix things, thanks!
Yep, and making it extra portable, probably checking for '-P' option presence should precede actual 'cc -E' call.