https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2187
This bugzilla entry is similar to what I've reported:
configure finds the header of some 3.x version of Berkeley DB, but
linking is tried with db-4.0.
Can this be fixed in a way that will allow linking with db3.x ?
Thank you,
Adrian Buciuman
> bdb-libdir will determine -L linker option, while bdb-incdir will
> determine -I (uppercase i) option and indirectly, via version in the
> header, -l (lowercase L) option, the version known internally by cyrus
> and optionally rpath.
>
> Regards,
> Adrian Buciuman
>
Sorry, I've made a mistake.
> Not exactly what you want, but on a Slackware 10.2 system, I use these
> options:
>
> ./configure --prefix=/usr \
>--with-bdb-libdir=DIR=/usr/lib \
>--with-bdb-incdir=/usr/include/db4
>
I know this works . However, I use db3.3.
Cyrus should not impose me to use a particular version of
Adrian Buciuman wrote:
On 12/12/05, Ken Murchison <[EMAIL PROTECTED]> wrote:
I am pleased to announce the release of Cyrus IMAPd 2.3.0. This is an
BETA-quality release
I'm trying to compile it on Slackware.
How can I elegantly select which Berkeley DB to use?
I want to use libdb-3.3, which
On 12/12/05, Ken Murchison <[EMAIL PROTECTED]> wrote:
> I am pleased to announce the release of Cyrus IMAPd 2.3.0. This is an
> BETA-quality release
I'm trying to compile it on Slackware.
How can I elegantly select which Berkeley DB to use?
I want to use libdb-3.3, which is the system default,
