Cyrus-SASL 2.1.23 / 2.1.24 and Heimdal 1.4

[Dan White]

On 04/10/10 13:17 +0200, Remi Ferrand wrote:
>But pluginviewer shows up that GSSAPI mechanism isn't available...
>
># /opt/cyrus/sbin/plugiviewer
  
>Something strange happens ... the gssapi plugin is present and linked to
>the correct Heimdal libs:
>
># ldd /opt/cyrus/lib/sasl2/libgssapiv2.so
>        libgssapi.so.2 =>        /opt/heimdal/lib/libgssapi.so.2
  
>A truss on the pluginviewer process reveals that libkrb5 and libgssapi
>from heimdal libs are correctly found and everything seems okay from
>this point of view.
>
>Everything seems okay but pluginviewer doesn't consider GSSAPI has an
>available SASL mechanism. It means that GSSAPI plugin can't be loaded,
>isn't it ?

Did you pass a '--with-plugindir' value in configure to point to
/opt/cyrus/lib/sasl2? If not, the sasl glue library will search for shared
libraries in /usr/lib/sasl2 regardless of the '--prefix' option passed.

The install file discusses the reasoning behind that:

http://www.cyrusimap.org/docs/cyrus-sasl/2.1.23/install.php

If pluginviewer is looking in the right location but still not initializing
the gssapi plugin correctly, you might get some details about the problem
in the auth.debug syslog facility. See:

http://www.cyrusimap.org/docs/cyrus-imapd/2.3.16/install-configure.php

-- 
Dan White