HI!
This seems to be already fixed:
ITS#8056: libdb detection with gcc 5
But gcc-5.1.1 arrived on openSUSE Tumbleweed and now libdb detection fails:
checking db.h usability... yes checking db.h presence... yes 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
From config.log:
configure:20300: checking db.h usability configure:20300: cc -c -g -O0 -DSLAP_SCHEMA_EXPOSE -DLDAP_COLLECTIVE_ATTRIBUTES -DSLAP_CONFIG_DELETE -I/usr/include -I/usr/include -I/usr/include -I/usr/include conftest.c >&5 configure:20300: $? = 0 configure:20300: result: yes configure:20300: checking db.h presence configure:20300: cc -E -I/usr/include -I/usr/include -I/usr/include -I/usr/include conftest.c configure:20300: $? = 0 configure:20300: result: yes configure:20300: checking for db.h configure:20300: result: yes configure:20311: checking for Berkeley DB major version in db.h configure:20331: result: none configure:20334: error: Unknown Berkeley DB major version in db.h
Any clue?
Ciao, Michael.
On Sat, 4 Jul 2015, Michael Str?der wrote:
HI!
This seems to be already fixed:
ITS#8056: libdb detection with gcc 5
But gcc-5.1.1 arrived on openSUSE Tumbleweed and now libdb detection fails:
Bottom line, set CPP='cpp -P' during configure. (Dunno why the m4 patch didn't take if you're on a patched copy; perhaps autoconf needs to be re-run...)
details:
gcc added cpp -P with behavior of traditional cpp -E, and changed cpp -E to emit detailed line number information (desirable when debugging complex macros etc.). This confuses autoconf.
https://bugzilla.redhat.com/show_bug.cgi?id=1191098
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64864
checking db.h usability... yes checking db.h presence... yes 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
From config.log:
configure:20300: checking db.h usability configure:20300: cc -c -g -O0 -DSLAP_SCHEMA_EXPOSE -DLDAP_COLLECTIVE_ATTRIBUTES -DSLAP_CONFIG_DELETE -I/usr/include -I/usr/include -I/usr/include -I/usr/include conftest.c >&5 configure:20300: $? = 0 configure:20300: result: yes configure:20300: checking db.h presence configure:20300: cc -E -I/usr/include -I/usr/include -I/usr/include -I/usr/include conftest.c configure:20300: $? = 0 configure:20300: result: yes configure:20300: checking for db.h configure:20300: result: yes configure:20311: checking for Berkeley DB major version in db.h configure:20331: result: none configure:20334: error: Unknown Berkeley DB major version in db.h
Any clue?
Ciao, Michael.
Aaron Richton wrote:
On Sat, 4 Jul 2015, Michael Ströder wrote:
HI!
This seems to be already fixed:
ITS#8056: libdb detection with gcc 5
But gcc-5.1.1 arrived on openSUSE Tumbleweed and now libdb detection fails:
Bottom line, set CPP='cpp -P' during configure. (Dunno why the m4 patch didn't take if you're on a patched copy; perhaps autoconf needs to be re-run...)
Sigh! Yes, re-running autoconf fixes it.
Also fixes Factory builds here:
https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap/...
Normally when packaging software running autoconf on release tar-balls is considered rather bad practice.
Wouldn't this justify to re-roll a OpenLDAP release?
Ciao, Michael.
--On Saturday, July 04, 2015 6:27 PM +0200 Michael Ströder michael@stroeder.com wrote:
Wouldn't this justify to re-roll a OpenLDAP release?
First step would be to file an ITS. Please do so. :)
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Quanah Gibson-Mount wrote:
--On Saturday, July 04, 2015 6:27 PM +0200 Michael Ströder
Wouldn't this justify to re-roll a OpenLDAP release?
First step would be to file an ITS. Please do so. :)
http://www.openldap.org/its/index.cgi?findid=8189
Ciao, Michael.
--On Monday, July 06, 2015 7:21 PM +0200 Michael Ströder michael@stroeder.com wrote:
Quanah Gibson-Mount wrote:
--On Saturday, July 04, 2015 6:27 PM +0200 Michael Ströder
Wouldn't this justify to re-roll a OpenLDAP release?
First step would be to file an ITS. Please do so. :)
Yeah, I spoke too soon. This is actually ITS#8056, I just missed the need to regenerate configure.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration