On 09/09/2009 11:56 AM, Klaus Heinrich Kiwi wrote: > * The old behavior was to build the pkcs11 support unless > --disable-pkcs11-support was specified > * for some reason, '--enable-pkcs11-support' was in fact disabling > the feature, instead of enforcing it's build (like I was expecting) > * the new behavior is as follows: > > --with-pkcs11 or --with-pkcs11=yes (default): > enable pkcs11, error if no header is found > > --without-pkcs11 or --with-pkcs11=no: > disable pkcs11, no check is made > > --with-pkcs11=check > check and enable pkcs11 if header is found, disable otherwise
Oh and the previous behavior was more like the --with-pkcs11=check -Klaus -- Klaus Heinrich Kiwi | [email protected] | http://blog.klauskiwi.com Open Source Security blog : http://www.ratliff.net/blog IBM Linux Technology Center : http://www.ibm.com/linux/ltc ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ TrouSerS-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-tech
