When I installed cyrus on my Debian Potato
system I compiled SASL to use GDBM instead
of Berkeley DB.
The rest of the system used db3.
-- Michael --
----- Original Message -----
From: "Olaf Zaplinski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 05, 2001 3:54 AM
Subject: Re: Compilation probs:- ldb-3
> GOMBAS Gabor wrote:
> >
> > On Wed, Apr 04, 2001 at 11:20:18PM +0200, Olaf Zaplinski wrote:
> >
> > > For me, the only way to make it work is to get a distro with 'built
in' db3
> > > (SuSE 7.1). Reason: even if you get all db3 stuff installed and
configure
> > > accepts it (yup, that's what I did on a Debian box), the binary will
be
> > > linked with db2 => segfaults. And of course you cannot just deinstall
db2...
> >
> > I got curious and tried to build cyrus-imapd-2.0.12 on a Debian/Woody
box
> > (DB3 built from sources), and could not find a single binary that got
linked
> > with DB2. Something is really broken on your system. My first guess
would
> > be you forgot to rebuild Cyrus-SASL with DB3...
>
> Yup, it is Debian that must be broken... I have two potato boxes here
(woody
> is still unstable and so 'forbidden' to be used as a production system
> here).
>
> I can compile the cyrus stuff with db3 just like Mark Sweney explained to
> us. Even sendmail compiles without errors when linked against db3, but it
> then always segfaults on startup => no db3 for Debian potato.
>
> I am giving up. No IMAPD for our customers then... only for me with my
SuSE
> box... ;-)
>
> Olaf
>
