Problem with xmlsec

Roland Hedberg roland.hedberg at adm.umu.se
Mon Mar 1 23:20:35 PST 2010


On Mar 1, 2010, at 20:45, Ryan Schmidt wrote:

> On Mar 1, 2010, at 13:03, Roland Hedberg wrote:
> 
>> I'm a long time happy user of macports, who now has a problem.
>> On a new, pristine you could say, machine running 10.6.2 I've tried to install xmlsec.
>> 
>> The installation as such works without a flaw but when I try to encrypt/decrypt with /opt/local/bin/xmlsec1 I get the complaint:
>> 
>> Error: unable to load xmlsec-openssl library. 
>> 
>> A couple of lines higher up I get the impression that it tries to load libxmlsec1-openssl.so
>> 
>> In /opt/local/lib there are different versions of libxmlsec1-openssl:
>> 
>> -rwxr-xr-x  2 root  admin  1435136  1 Mar 15:26 /opt/local/lib/libxmlsec1-openssl.1.2.13.dylib
>> lrwxr-xr-x  1 root  admin       31  1 Mar 15:26 /opt/local/lib/libxmlsec1-openssl.1.dylib -> libxmlsec1-openssl.1.2.13.dylib
>> -rw-r--r--  2 root  admin  5486024  1 Mar 15:26 /opt/local/lib/libxmlsec1-openssl.a
>> lrwxr-xr-x  1 root  admin       31  1 Mar 15:26 /opt/local/lib/libxmlsec1-openssl.dylib -> libxmlsec1-openssl.1.2.13.dylib
>> -rwxr-xr-x  2 root  admin     1026  1 Mar 15:26 /opt/local/lib/libxmlsec1-openssl.la
>> -rwxr-xr-x  2 root  admin   421672  1 Mar 15:26 /opt/local/lib/libxmlsec1.1.2.13.dylib
>> lrwxr-xr-x  1 root  admin       23  1 Mar 15:26 /opt/local/lib/libxmlsec1.1.dylib -> libxmlsec1.1.2.13.dylib
>> -rw-r--r--  2 root  admin   659960  1 Mar 15:26 /opt/local/lib/libxmlsec1.a
>> lrwxr-xr-x  1 root  admin       23  1 Mar 15:26 /opt/local/lib/libxmlsec1.dylib -> libxmlsec1.1.2.13.dylib
>> -rwxr-xr-x  2 root  admin      941  1 Mar 15:26 /opt/local/lib/libxmlsec1.la
>> 
>> But as you can see none of them ends with '.so' .
>> I've used DYLD_LIBRARY_PATH to ensure that it tries /opt/local/lib first, but to no avail.
>> 
>> Could it be that LTDL_SHLIB_EXT is not set properly, in that case how do I ackomplish that ?
> 
> I see the same problem. Updating to 1.2.14 changes the error slightly but does not eliminate it. Updating to 1.2.14 is not straightforward because the configure patch no longer applies and I do not understand its purpose so I'm ill-equipped to update the patch. The problem with the shared library extension not being properly detected should be reported to the developers of xmlsec most likely.

Aleksey's answer is to point to http://www.aleksey.com/pipermail/xmlsec/2004/006046.html

--Roland



More information about the macports-users mailing list