]: *** [sasldblistusers.o] Error 1
Olaf
> - 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:
&
Hey,
thanks for all your help good people. I'll certainly have another go
when I get into work today.
Regards,
Paul Dorman.
, 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
> > > (S
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 Debi
In my experience, if your berkeley DB3 libraries are named `libdb-3.X'
then you won't have any problems with this, if they're `libdb3.X' then it
might find them but still uses -ldb (something like that, it was the
only way I could get cyrus to build without manually editing the
Makefiles).
Scott
At 12:32 PM 4/4/2001 +1200, paul wrote:
>Hi all,
>
>downloaded 2.0.12 and ran into problems during the ./configure process.
>It bailed when looking for a properly configured db3 install. I didn't
>have it, so I downloaded and installed the appropriate db3 and db3-devel
>rpms from rpmfind.net. Stil
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
> lin
paul wrote:
>
> Hi all,
>
> downloaded 2.0.12 and ran into problems during the ./configure process.
> It bailed when looking for a properly configured db3 install. I didn't
> have it, so I downloaded and installed the appropriate db3 and db3-devel
> rpms from rpmfind.net. Still failed, which I t
