Greetings,

On Fri, 5 Jan 2001, GOMBAS Gabor wrote:

> 
> It seems you have built cyrus-sasl against a different Berkeley DB library.
>
> > On the other hand, as has been previously pointed out, cyrus-imap requires
> > libdb-3.a to compile.  By renaming the db3 libdb.a to libdb-3.a and
> > leaving both libdb's in /usr/lib, and copying db3's db.h to
> > /usr/include/db-3.h I have been able to get cyrus-imap to compile (after
> > changing a number of #include <db.h> to #include <db-3.h>)
> 
> No need for that. Just put the DB3 includes under the /usr/include/db3 
> directory and give the configure script the "--with-dbdir=/usr" parameter.
> Although I'd prefer using /usr/local and leaving /usr alone...
>
Thanks for the pointers...I did as you suggested, and compiled both sasl
and imap with statically linked libraries.  That at least got them both
to compile.  However, I am still confused about why the instructions 
recommend compiling libsasl and imap with the same version of Berkely DB,
even though that seems not to work.  Perhaps I have a deeper
misunderstanding of the situation to resolve.


Now, I have a new problem.  When running 
 /usr/local/bin/imtest -t "" my.server

I get the error message
C: C01 CAPABILITY
failure: prot layer failure

Running strace on this command shows the following

open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT
(No su
ch file or directory)
open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No
such
file or directory)
write(1, "C: C01 CAPABILITY\r\nfailure: prot"..., 47C: C01 CAPABILITY
failure: prot layer failure
) = 47
munmap(0x141000, 4096)                  = 0
_exit(1)                                = ?


I have searched high and low for a libc.mo to install on my system 
(Linux Mandrake 7.2) but none of the locale libraries or glibc seem
to have one in the /en/ directory.

What is the purpose of libc.mo, exactly, and is there any way to get past
this point without it, or where could I should look for it?

Thanks for the help,

Barry

Reply via email to