[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Headache with IMAP
I thought that was the problem, then I scrapped the whole system and
started all over again. If you notice in the package, it creates a symbolic
link from /usr/local/lib/sasl to /usr/lib/sasl. That's not the issue. After
some more investigation, I realized that the package installed the wrong
symbolic links to the files that can't be dl_opened. It seems that there is
a slight problem with the port.
/usr/local/lib/sasl/libplain.so was pointing to libplain.so.1.13 when the
filename was libplain.so.1.14. Hehehehehe, that looks like a big problem.
So, I fixed it, but now the syslog doesn't report anything and it still
doesn't work....
I'm beating my head into a wall right now, if it doesn't work I'll simply
install Debian because they have it packaged.
Regards,
Patrick Ethier
patrick@secureops.com
At 03:46 PM 19/12/2000 -0800, you wrote:
>Patrick Ethier writes:
> > The log file reports and these files are all where they are supposed
> to be...
> >
> > Dec 19 13:46:12 herald imtest: unable to dlopen
> > /usr/lib/sasl/libanonymous.so: No such file or directory
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>Apparently the cyrus-sasl port was not installed correctly. If it was
>the needed files would be in /usr/local/lib/sasl (not /usr/lib/sasl)
>and the proper symbolic links would have been created. I don't know
>why or how the problem occurred. I'd try something like:
>
> $ su
> # pkg_delete cyrus-sasl-1.5.24
> # ^D
> $ cd /usr/ports/security/cyrus-sasl
> $ make clean
> $ make
> $ su
> # make install
>
>and check that /usr/local/lib/sasl exists, contains the needed shared
>libs, and also contains the symbolic links that point the .so name
>to the numbered name.
>
>Hmm, a thought. Did you one time NOT use the port? That would explain
>why /usr/lib/sasl/ exists. If /usr/lib/sasl and /usr/local/lib/sasl both
>exist you MUST remove /usr/lib/sasl as configure will find it and not
>use correct version in /usr/local/lib/sasl.
>
>// marc