You can see it being picked up twice. I suppose libcrypto shouldn't be there at all,
but be linked against the application only?
Yes. But I don't think it can create any problems. Linker will strip out all the crap anyway :)
Also, the static libcrypto is being linked against the dynamic libxmlsec1-openssl.so.
I noticed that because of the warning
*** Warning: Linking the shared library libxmlsec1-openssl.la against the
*** static library /usr/lib/libcrypto.a is not portable!
Is there a special reason for not linking against dynamic libcrypto ?
xmlsec tries to find either shared or static openssl library. And then links against the first thing it finds.
Aleksey
_______________________________________________ xmlsec mailing list [email protected] http://www.aleksey.com/mailman/listinfo/xmlsec
