From: Donny Davies <woodchip@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] [fwd] RE: compiling 2.1.22 with db 4.0.x (from: hyc@highlandsun.com)
Date: Wed, 23 Jul 2003 16:31:37 -0400 [thread overview]
Message-ID: <20030723203137.GA9346@breccia.escarpment> (raw)
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
----- Forwarded message from Howard Chu <hyc@highlandsun.com> -----
From: Howard Chu <hyc@highlandsun.com>
To: tarjei@nu.no, openldap-software@OpenLDAP.org
Date: Wed, 23 Jul 2003 11:49:21 -0700
Subject: RE: compiling 2.1.22 with db 4.0.x
Message-ID: <007b01c3514b$28c65730$856350c1@CELLO>
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Sender: owner-openldap-software@OpenLDAP.org
Comment: openldap-software mailing list <http://www.OpenLDAP.org/lists/>
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Tarjei Huse
> Hi,
> Is it possible to compile the latest OpenLDAP against Sleepycat dB
> 4.0.x? If not, why? What is the latest version where this may be done?
> Tarjei
In software, anything is possible. Some things are not advisable, though.
In this case, BDB 4.0 has a number of resource leaks and other bugs that will
cause slapd to lockup after running for some period of time. I ran into these
bugs while developing back-bdb originally, and I never checked to see if they
also affect back-ldbm. It's possible, but I don't know. If you manually edit
the configure script to bypass the version check, you can use BDB 4.0 with
the latest OpenLDAP release if you really want to. But that would really be
asking for trouble.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
http://www.symas.com http://highlandsun.com/hyc
Symas: Premier OpenSource Development and Support
----- End forwarded message -----
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-07-23 20:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030723203137.GA9346@breccia.escarpment \
--to=woodchip@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox