1) xmlsec is looking in the lib/ folder because this is
how openssl is usually installed. If you build openssl from
sources, then you have to do 'make install' to make it work.
2) The shrew vs shrext_cmds issue is a know one. I believe
that the current code in CVS should have it fixed
http://www.aleksey.com/pipermail/xmlsec/2005/002897.html
Though you might need to run ./autoconf.sh manually.
Aleksey
Dmitry Belyavsky wrote:
Greetings!
I've found a problem configuring xmlsec with openssl.
Xmlsec expects shared libraries in $with_openssl/lib though the
directory $with_openssl/lib is not created on building openssl. Besides,
the $shrext configure variable seems to be empty.
The patch is attached.
------------------------------------------------------------------------
Index: configure
===================================================================
RCS file: /cvs/xmlsec/configure,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- configure 6 Dec 2005 09:29:13 -0000 1.1.1.1
+++ configure 17 Jan 2006 09:12:08 -0000 1.2
@@ -25070,8 +25070,10 @@
echo "${ECHO_T}no" >&6
elif test "z$with_openssl" != "z" ; then
OPENSSL_CFLAGS="$OPENSSL_CFLAGS -I$with_openssl/include"
- if test -f "$with_openssl/lib/libcrypto$shrext" ; then
+ if test -f "$with_openssl/lib/libcrypto$shrext_cmds" ; then
OPENSSL_LIBS="-L$with_openssl/lib -lcrypto -ldl"
+ elif test -f "$with_openssl/libcrypto$shrext_cmds" ; then
+ OPENSSL_LIBS="-L$with_openssl -lcrypto -ldl"
else
OPENSSL_LIBS="$with_openssl/lib/libcrypto.a -ldl"
fi
------------------------------------------------------------------------
_______________________________________________
xmlsec mailing list
[email protected]
http://www.aleksey.com/mailman/listinfo/xmlsec
_______________________________________________
xmlsec mailing list
[email protected]
http://www.aleksey.com/mailman/listinfo/xmlsec
