[Pkg-openldap-devel] DEBIAN / UBUNTU OPENLDAP WILL NOT BUILD FROM SOURCE

[Ryan Tandy]

On Sun, May 22, 2016 at 04:02:32PM -0500, GI Joe wrote:
>If you can create a VM of ubuntu 14.04, 1604 OR Debian 8....

schroot -c xenial-amd64 -u root

✓

>1) apt-get your build dependencies and build tools.

apt-get install devscripts ubuntu-dev-tools
apt-get build-dep openldap

✓

>2) apt-get source slapd.

Get:1 http://ca.archive.ubuntu.com/ubuntu xenial/main openldap 2.4.42+dfsg-2ubuntu3 (dsc) [3,032 B]
Get:2 http://ca.archive.ubuntu.com/ubuntu xenial/main openldap 2.4.42+dfsg-2ubuntu3 (tar) [4,813 kB]
Get:3 http://ca.archive.ubuntu.com/ubuntu xenial/main openldap 2.4.42+dfsg-2ubuntu3 (diff) [176 kB]

✓

>[edit your configure.options as you wish (FYI... I usually enable *all*
>backends and overlays... and use tls=openssl)]

I'm going to stick with the configuration shipped in the package, for 
the moment.

(I was expecting a 'dch --local', or some other edit to 
debian/changelog, at this point, to distinguish your package from the 
archive version...)

>3) dh binary
>
>That SHOWS you everything you need to know.

I think you want 'debian/rules binary' or some sort of dpkg-buildpackage 
command. See below.

>-----------------------------
>
>I've deleted out all of the overrides in debian/rules (virtually everything
>special regarding anything in ./contrib/slapd-modules)

OK. Why? Is this to work around the contrib modules (specifically 
smbk5pwd) being set up to build with gnutls, while you're building with 
openssl?

>
>I've also added blank var VERSION_OPTIONS= and GSSAPI_LIBS to configure.in
>

Why?

>Doing all of that allows a complete compile and, as I type this msg to you,
>it's running the tests.

Over here, running just 'dh binary' failed to compile. I have a 
suspicion about why that is: 'debian/rules binary' doesn't invoke just 
'dh binary', but a longer command:

dh binary --with autoreconf --builddirectory=/.../openldap-2.4.42+dfsg/debian/build --parallel

Missing '--with autoreconf' might explain why you find yourself having 
to edit configure.in, while missing --builddirectory would explain the 
error about missing libtool I remarked on earlier.

'debian/rules binary' also failed for me, which I wasn't expecting: 
configure failed in the gssapi part, and I'm not sure why.

'dpkg-buildpackage -us -uc -b' does succeed for me, though, with no 
changes at all to the package. So maybe try using that instead?