Michele Calgaro wrote: > If you are building using jessie (as you mentioned in another email) it > sounds a little strange you had to disable pkcs support. openssl in jessie > is still at 1.0.1 (or 1.0.2 with backport)... Just for info only. There were also some other minor things, but I was having another goal. Perhaps when scripts are available I will setup a build env and report on issues with that. For the openssl you are correct. I have openssl 1.0.1t here. $ dpkg -l | grep openssl ii libevent-openssl-2.0-5:amd64 2.0.21-stable-2 amd64 Asynchronous event notification library (openssl) ii libgnutls-openssl27:amd64 3.3.8-6+deb8u3 amd64 GNU TLS library - OpenSSL wrapper ii openssl 1.0.1t-1+deb8u5 amd64 Secure Sockets Layer toolkit - cryptographic utility ii openssl-blacklist 0.5-3 all Blacklists for OpenSSL RSA keys and tools ii python-openssl 0.14-1 all Python 2 wrapper around the OpenSSL library regards --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
