"Kevin M. Myer" wrote:
>
> Hello,
>
> This is mainly for archive purposes in case anyone else has the same
> problems I did and thinks to search the archives first.
>
> I have spent quite a few hours trying to figure out why my sieve vacation
> scripts were not working with postfix. I upgrad
This is what I just did a minute ago on my Red Hat 7.1, and it made
libsasl.so link against libdb-3.3.so. I may or may not work on Mandrake 7.2,
but it is worth a shot.
With BerkeleyDB installed in /usr/local/BerkeleyDB.3.3, I did
./configure
make CPPFLAGS="-I/usr/local/BerkeleyDB.3.3/include
I had a very similar problem compiling on HPUX--when I ran configure, even
with the LDFLAGS and CPPFLAGS set correctly, the makefiles were not built
with those dependencies in the correct order. I had to manually go into each
Makefile in each subdirectory and make sure it linked against the correc
Hello,
This is mainly for archive purposes in case anyone else has the same
problems I did and thinks to search the archives first.
I have spent quite a few hours trying to figure out why my sieve vacation
scripts were not working with postfix. I upgraded my Berkeley DB
libraries from 3.1.17
Hi Kohei,
> > > If you have any of db[123] rpms installed, can you uninstall
> > > them without
> > > breaking dependencies?
> >
> > What should this help???
>
> I was just trying to see if your system already had previous
> version(s) of
> Berkeley DB libraries (db1, db2 and db3 are it). SASL
>
> What does
> cd /lib
> ls -la libdb.so.3
> show on your system???
# ls -la libdb.so.3
lrwxrwxrwx1 root root 14 Feb 16 2001 libdb.so.3 ->
libdb-2.1.3.so*
> An how does your ld.so.conf look like???
# cat /etc/ld.so.conf
/usr/X11R6/lib
/usr/i486-linux-libc5/lib
> > # rpm -qa
Hi,
> > > Did you do a recompilation of cyrus-sasl after the
> > > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.so
> > >
> > > > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.a
> > >
> > > stuff???
> >
> O.K. I'll try to recompile cyrus-sasl with the above symlinks. I've
> already added them.
I
Hi Kohei,
> $ ldd libsasl.so
> libdb-3.3.so => /usr/lib/libdb-3.3.so (0x4001c000)
> libdl.so.2 => /lib/libdl.so.2 (0x4009b000)
> libcrypt.so.1 => /lib/libcrypt.so.1 (0x4009f000)
> libpam.so.0 => /lib/libpam.so.0 (0x400cc000)
> libresolv.so.2 => /lib/libresolv.so.2 (0x400d5000)
> libc.so.6 => /lib
On Wednesday 10 October 2001 02:33, you wrote:
> Hi Kohei,
>
> > Try
> >
> > cd /usr/lib
> > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.so
> > ln -s /usr/local/BerkeleyDB.3.3/lib/libdb-3.3.a
>
> Didn't have any effect on my system.
>
> - Did you have an signaled to death (11) as well?
No I did
Thanks Ralph... I had not tried that before, however
this did not seem to work for me:
It seems that the admins section of the imapd.conf is
not working
**telnet session:
telnet imap 143
Trying xxx.xxx.xxx.xxx...
Connected to imap.goob.com.
Escape character is '^]'.
* OK imap.goob.com Cyrus I
Awhile back, I seem to recall someone (Amos Gouaux I believe) commenting
about one of the limitations of the LDAP patch to the SASL library was
that it didn't support realms. This is now becoming an issue for me,
since I am supporting multiple domains and since there is the potential
for user
11 matches
Mail list logo
