Created attachment 11352 [details]
rpm buildlog of an openSUSE 13.2 x86_64 build
Building with --bundled-libraries=!ldb,!pyldb worked for 4.2 and earlier
I've tried a manual configure && make too. The full list of configure
options while the failing manual build had been:
You need to install pyldb-util, see:
Author: Jelmer Vernooij <email@example.com>
AuthorDate: Wed Jan 21 02:58:49 2015 +0100
Commit: Andreas Schneider <firstname.lastname@example.org>
CommitDate: Tue Feb 17 15:41:11 2015 +0100
Force rebuild of ldb if pyldb-util is not available.
This is necessary since pyldb-util uses ldb_private.h, so we want to
build against the same source ldb.
Signed-off-by: Jelmer Vernooij <email@example.com>
Reviewed-by: Andreas Schneider <firstname.lastname@example.org>
Created attachment 11353 [details]
config.log bzip2 compressed
Created attachment 11354 [details]
pyldb-devel-1.1.21 is installed which provides:
It is present on the system where I called configure manually too.
Metze is right with his comment #1 Commit
fcf4a891945b22dc6eccdc71fd441f1a879f556a causes this issue.
The system used for a manual configure had fitting pyldb, ldb, and devel
packages installed. The build service ensures this anyhow. And that's
also visible from the build log attached with the initial comment.
Can you reproduce this if you also specify !pyldb-util?
*** Bug 11468 has been marked as a duplicate of this bug. ***
If I specify
I get the following error:
ERROR: Use of system library pyldb-util depends on missing system library/libraries ['ldb']
configure did not search for system ldb before this error occurred.
krikkit:~ # rpm -ql pyldb
krikkit:~ # rpm -ql pyldb-devel
Have you tried not spelling pyldb-util as "pyld-util" ? :P
as additional --bundled-libraries argument results in:
[ 67s] Checking for python headers : using cache
[ 67s] ERROR: Use of system library pyldb-util depends on missing system library/libraries ['ldb']
[ 67s] error: Bad exit status from /var/tmp/rpm-tmp.26nyUv (%build)
Comment #10 was the reply to comment #6.
Created attachment 11369 [details]
config.log with added !pyldb-util as requested with comment #6
Hmm, I think you might also have to specify !talloc,!tdb,!tevent and possibly other dependencies of ldb.
FWIW, in Debian we do build against the system ldb, pyldb and pyldb-util by specifying the following:
!talloc,!tdb,!tevent and many more are excluded.
For the full list see the initial comment plus the later added !pyldb-util
Also trying --bundled-libraries=NONE results in the same:
[ 68s] Checking for Python version >= 2.4.2 : ok 2.7.8
[ 68s] Checking for python headers : using cache
[ 68s] ERROR: Use of system library pyldb-util depends on missing system library/libraries ['ldb']
I suspect this is a regression from Petr's changes (https://lists.samba.org/archive/samba-technical/2015-August/108972.html). We now check for system pyldb-util *before* checking for ldb itself. Since pyldb-util depends on ldb, this breaks.
See line 58 of lib/ldb/wscript in master
Created attachment 11371 [details]
Possible patches for master
(In reply to Jelmer Vernooij from comment #16)
Jelmer, the problem is really your commit fcf4a891945b22dc6eccdc71fd441f1a879f556a.
The onlyif list for the pyldb-util check contains 'ldb', but
the check for ldb is not yet done.
If it still works with --bundled-libraries=NONE,... it's pure luck.
Lars, Andreas, I think using --bundled-libraries=NONE,...
and listing explicit what will be bundled would be
a better way for your spec files.
Created attachment 11386 [details]
Patch for v4-3-test
Pushed to autobuild-v4-3-test.
Pushed to v4-3-test