On Sun, Sep 9, 2012 at 8:22 AM, Graham Leggett <minf...@sharp.fm> wrote: > On 08 Sep 2012, at 5:23 PM, Jeff Trawick wrote: > >> Enabling a particular crypto library by default would only be done if >> --with-crypto was requested. The global default (no crypto) wouldn't >> change. But if you enable the crypto feature you could avoid having >> to specify a particular implementation, unless the search path had to >> be overridden. > > This sounds sensible. I'd say default --with-openssl and --with-nss to on, > and respect the default value of --with-crypto.
Hopefully r1389126 does the right thing... > > Regards, > Graham > -- > -- Born in Roswell... married an alien... http://emptyhammock.com/