Yes, you are right. This is a bug :( Fix is checked in CVS. Thanks for reporting this and all other issue! I am really glad to have someone who looks in all these configuration files!
Aleksey
Index: xmlsec-config.in =================================================================== RCS file: /cvs/gnome/xmlsec/xmlsec-config.in,v retrieving revision 1.13 diff -u -r1.13 xmlsec-config.in --- xmlsec-config.in 10 Sep 2003 07:55:26 -0000 1.13 +++ xmlsec-config.in 12 Jan 2004 18:29:50 -0000 @@ -168,7 +168,7 @@ ;;
nss)
- if test "@XMLSEC_NO_NSS@" = "no"; then
+ if test "@XMLSEC_NO_NSS@" = "0"; then
the_crypto_flags="@NSS_CFLAGS@ -DXMLSEC_CRYPTO=\\\"nss\\\""
the_crypto_libs="@NSS_LIBS@"
the_xmlsec_crypto_lib="[EMAIL PROTECTED]@"John Belmonte wrote:
Even though I enabled nss in my build and it appears as a crypto option in the xmlsec1-config help, selecting this engine yields an error. In the xmlsec1-config script I see something that looks suspicious:
nss) if test "0" = "no"; then
-John
_______________________________________________ xmlsec mailing list [EMAIL PROTECTED] http://www.aleksey.com/mailman/listinfo/xmlsec
