Cyrus IMAP 2.1.12 and Berkeley 4.1.25

[Joe Rhodes]

Patrick:

DOH!  I forget the simplest things.  Looks like it is an issue with the 
mutex that's being auto selected:

configure:2848: checking for db_create in -ldb-4.1
configure:2867: gcc -o conftest -Wall -g -O2  -L/usr/local/lib
-Wl,-rpath,/usr/local/lib  conftest.c -ldb-4.1   -lresolv  1>&5
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../libdb-4.1.so: 
undefined reference to `pthread_condattr_setpshared'
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../libdb-4.1.so: 
undefined reference to `pthread_mutexattr_destroy'
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../libdb-4.1.so: 
undefined reference to `pthread_mutexattr_setpshared'
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../libdb-4.1.so: 
undefined reference to `pthread_mutexattr_init'
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../libdb-4.1.so: 
undefined reference to `pthread_mutex_trylock'
collect2: ld returned 1 exit status
configure: failed program was:
#line 2856 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error.  */
/* We use char because int might match the return type of a gcc2
     builtin and then its argument prototype would still apply.  */
char db_create();

int main() {
db_create()
; return 0; }


I get this same thing with each of the database versions  in turn that 
it tries.

Now the bigger question, is this more an issue with by version of gcc 
(I've seen some mention of that on other lists) or is there a flag I 
can feed to the Berkeley DB ./configure to get around this.  I'll do 
some experimentation with the latter.

Any insights (or perhaps someone who'd conquered this demon all ready) 
always welcome.

Cheers!
-Joe

On Friday, May 2, 2003, at 11:21  AM, Patrick Morris wrote:

> My first suggestion would be to take a look at config.log to see why 
> it's failing.
>
> Joe Rhodes wrote:
>
>> Again, BerkeleyDB packages were compiled with --prefix=/usr flag.  
>> I've looked through the sleepy cat docs, but I don't see anything 
>> terribly obvious that jumps out at me.  If anyone has some 
>> suggestions?
>
>
>
>
>
>