#47615 Failed to compile the DS 389 1.3.2.3 version against Berkeley DB 4.2 version
Closed: wontfix Opened by rmeggins.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1033154

Description of problem:
I downloaded 389 directory server source code 1.3.2.3 from link
(http://port389.org/sources/389-ds-base-1.3.2.3.tar.bz2) and try to compile in
my CentOS release 4.9 (Final) environment. I noticed below error message and
suspect with referring invalid Berkeley DB version.  I am currently using
Berkeley DB version is db4-4.2.52-7.3.el4 and the link recommended the same.
http://directory.fedoraproject.org/wiki/Building#Berkeley_DB
It looks DS 1.3.2 release version support bdb 4.7 and above. This should
support for bdb 4.2 version as well.
[root@ ~]# rpm -qa | grep db4
db4-4.2.52-7.3.el4
db4-4.2.52-7.3.el4
[root@ ~]#
Error message:
In function `checkpoint_threadmain':
../ldap/servers/slapd/back-ldbm/dblayer.c:4789: error: `DB_COMPACT' undeclared
(first use in this function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4789: error: (Each undeclared
identifier is reported only once
../ldap/servers/slapd/back-ldbm/dblayer.c:4789: error: for each function it
appears in.)
../ldap/servers/slapd/back-ldbm/dblayer.c:4789: error: syntax error before
"c_data"
../ldap/servers/slapd/back-ldbm/dblayer.c:4791: error: `inst_obj' undeclared
(first use in this function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4794: error: `inst' undeclared (first
use in this function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4795: error: `rc' undeclared (first
use in this function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4795: error: `db' undeclared (first
use in this function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4809: error: `c_data' undeclared
(first use in this function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4809: error: `DB_FREE_SPACE'
undeclared (first use in this function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4691: error: label `error_return'
used but not defined
../ldap/servers/slapd/back-ldbm/dblayer.c: At top level:
../ldap/servers/slapd/back-ldbm/dblayer.c:4857: error: syntax error before '{'
token
../ldap/servers/slapd/back-ldbm/dblayer.c:4858: error: `li' undeclared here
(not in a function)
../ldap/servers/slapd/back-ldbm/dblayer.c:4858: error: initializer element is
not constant
../ldap/servers/slapd/back-ldbm/dblayer.c:4858: warning: data definition has no
type or storage class
../ldap/servers/slapd/back-ldbm/dblayer.c:4859: error: syntax error before ':'
token
../ldap/servers/slapd/back-ldbm/dblayer.c:4861: error: syntax error before '->'
token
../ldap/servers/slapd/back-ldbm/dblayer.c:4861: warning: data definition has no
type or storage class
Version-Release number of selected component (if applicable):
389 directory server source code 1.3.2.3
http://port389.org/sources/389-ds-base-1.3.2.3.tar.bz2
How reproducible:
Refer the description
Steps to Reproduce:
Refer the description
Actual results:
Expected results:
This should support for bdb 4.2 version as well.
Additional info:

git merge ticket47615
Updating b1e4cdf..80e39bc
Fast-forward
ldap/servers/plugins/replication/cl5_api.c | 2 ++
ldap/servers/slapd/back-ldbm/dblayer.c | 6 ++++++
2 files changed, 8 insertions(+), 0 deletions(-)

git push origin master
Counting objects: 19, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (10/10), done.
Writing objects: 100% (10/10), 1.08 KiB, done.
Total 10 (delta 8), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds.git
b1e4cdf..80e39bc master -> master

commit 80e39bce5c2d3649694bfce04822868c7256e022
Author: Mark Reynolds mreynolds@redhat.com
Date: Mon Feb 10 16:49:42 2014 -0500

1.3.2

7b08429..901dc5e 389-ds-base-1.3.2 -> 389-ds-base-1.3.2

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.2.12

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/952

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

Metadata