- **status**: open --> open-confirmed
- **assigned_to**: Daniel Stenberg
- **Priority**: 5 --> 3
- **Comment**:

Thanks for your report!

Yes, I agree it works exactly like that and I would agree it is the wrong behavior. I don't consider it a very high prio problem though...

---
** [bugs:#1358] ./configure --with-ssl should fail when SSL doesn't work**
**Status:** open-confirmed
**Created:** Thu Apr 10, 2014 11:59 PM UTC by Xiong Chiamiov
**Last Updated:** Thu Apr 10, 2014 11:59 PM UTC
**Owner:** Daniel Stenberg
    [$]> ./configure --with-ssl=/usr/local/ssl
    [snip]
    checking for CRYPTO_lock in -lcrypto... no
    checking for CRYPTO_add_lock in -lcrypto... no
    checking for ssl_version in -laxtls... no
    configure: WARNING: SSL disabled, you will not be able to use HTTPS, FTPS, NTLM and more.
    configure: WARNING: Use --with-ssl, --with-gnutls, --with-polarssl, --with-cyassl, --with-nss, --with-axtls, --with-winssl, or --with-darwinssl to address this.
    [snip]
When explicitly enabling SSL support, I expect a failure to appropriately find/link to/otherwise work with the SSL libraries to exit the script with a non-zero exit code.  Unfortunately, this is not the case; the process continues and exits successfully, which means Bash's `-e` doesn't catch it and I only come across errors much later in our server provisioning (that I have to trace back).
Latest version of curl, 7.36.0.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.