xmlsec: unable to load xmlsec-openssl library

[kurt@…]

% xmlsec1 --sign-tmpl --print-debug --ignore-manifests --privkey-pem ../xmlsec1-1.2.16/tests/keys/rsakey.pem --pwd secret sig.xml
func=xmlSecCryptoDLLibraryCreate:file=dl.c:line=130:obj=xmlsec_lt_dlopen:subj=unknown:error=7:io function failed:filename=libxmlsec1-openssl.so
func=xmlSecCryptoDLGetLibraryFunctions:file=dl.c:line=453:obj=unknown:subj=xmlSecCryptoDLLibraryCreate:error=1:xmlsec library function failed:crypto=openssl
func=xmlSecCryptoDLLoadLibrary:file=dl.c:line=404:obj=unknown:subj=xmlSecCryptoDLGetLibraryFunctions:error=1:xmlsec library function failed: 
Error: unable to load xmlsec-openssl library. Make sure that you have
this it installed, check shared libraries path (LD_LIBRARY_PATH)
envornment variable or use "--crypto" option to specify different
crypto engine.

This is likely due to the version of libtool used in the port not properly setting LTDL_SHLIB_EXT.

[ryandesign (Ryan Carsten Schmidt)]

Please remember to use WikiFormatting.

[ryandesign (Ryan Carsten Schmidt)]

Does r75092 help?

[kurt@…]

Your patch seems to alter the directory to be searched, not the suffix of the library of the dynamic library to be loaded. Hence, I would guess it wouldn't resolve this issue. If you believe it would, I'll give it a try when I'm next at my development station (tomorrow).

[kurt@…]

I note that a work around to this issue is:

# ln -s libxmlsec1-openssl.dylib libxmlsec1-openssl.so

Also, to test xmlsec1 is properly built and installed, one can go the examples directory and execute 'make all; make check'. This also a test suite which can be ran.

[ryandesign (Ryan Carsten Schmidt)]

Replying to kurt@…:

Your patch seems to alter the directory to be searched, not the suffix of the library of the dynamic library to be loaded. Hence, I would guess it wouldn't resolve this issue. If you believe it would, I'll give it a try when I'm next at my development station (tomorrow).

You may not have noticed that I also updated the port to version 1.2.16 in r75082, which no longer seems to have the .so vs. .dylib problem. After r75092, I no longer got the error you posted, but I don't really know anything about xmlsec so I don't know if it now works as it's supposed to.

[kurt@…]

Yes, I missed the version update.

The port is now working as I expect it to!

Thank you for you quick attention to this issue.

[ryandesign (Ryan Carsten Schmidt)]

I'm glad!