Plugins being found where they were not told to be found

[Jeff Blaine]

Turns out this is nothing more than our Cyrus IMAP
instance finding /usr/rcf/lib/libsasl2.so (when it
gets installed) before /hostname/mail/cyrus/lib/libsasl2.so
at runtime.

Because it finds the "wrong" libsasl2.so, it is of
course then going to reference that instance's copy
of the plugins.

Not for this list to solve :)

Thanks

Jeff Blaine wrote:
> Anyone?  This is holding up a lot of work.
> 
> Jeff Blaine wrote:
>> Our SASL build on a specific host (IMAP server) was
>> configured with:
>>
>>   --prefix=/hostname/mail/cyrus
>>
>> and
>>
>>   --with-plugindir=/hostname/mail/cyrus/lib/sasl2
>>
>> It has worked fine for years.
>>
>> For a separate need, I built and installed a separate
>> Cyrus SASL 2.1.22 instance using
>>
>>   --prefix=/usr/rcf
>>
>> and
>>
>>   --with-plugindir=/usr/rcf/lib/sasl2
>>
>> The previously mentioned IMAP server began immediately
>> failing because it was failing to find what it wanted
>> because it decided to start using /usr/rcf/lib/sasl2 !!
>>
>> What gives?
>>
>> :(
>>
>