lamlee cloudniw1 at gmail.com writes:
Douglas Mencken dougmencken at gmail.com writes:
just do the follow
./configure --with-ssh=openssl
then it will generate the Makefile,and then make install
Do you mean ./configure --with-ssl=openssl not ./configure --with-ssh=openssl?
Douglas Mencken dougmencken at gmail.com writes:
what is difficult about --with-ssl=openssl to configure?
What is difficult to specify the option which isn't ever mentioned in
README/INSTALL, nor in ./configure --help, nor in configure.ac? The
ability to find information.
On my side,
On Aug 13, 2011, at 12:34 PM, Douglas Mencken wrote:
If you want to use OpenSSL then you have to pass --with-ssl=openssl.
I hope this would be mentioned in README and/or INSTALL. And that
configure.ac will be fixed to say something better than stupid
--with-ssl was given, but GNUTLS is not
what is difficult about --with-ssl=openssl to configure?
What is difficult to specify the option which isn't ever mentioned in
README/INSTALL, nor in ./configure --help, nor in configure.ac? The
ability to find information.
On my side, going to GnuTLS means re-building and re-writing build
Perry Smith pedz...@gmail.com writes:
I took a stab at installing GNUTLS and gave up. The beauty of wget is
I can get it going with very few things needed. I compiled without ssl
at all but getting openssl going is fairly easy too. GNUTLS is asking
for nettle, zlib, and something else
Jochen Roderburg roderb...@uni-koeln.de writes:
And in general they seem to want to steer away the users from openssl
to gnutls and in order to do that the configure script doesn't even
mention this option any longer. :-(
And in the same vein the option --with-libssl-prefix has completely
If you want to use OpenSSL then you have to pass --with-ssl=openssl.
I hope this would be mentioned in README and/or INSTALL. And that
configure.ac will be fixed to say something better than stupid
--with-ssl was given, but GNUTLS is not available (especially, when
--with-ssl hasn't been
