Document that PKG_CONFIG_PATH is the preferred way to configure with

        ./configure --with-ssl

   If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL,)

   you can run configure like this:

   If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL)

   and you have pkg-config installed, set the pkg-config path first, like this:

        env PKG_CONFIG_PATH=/opt/OpenSSL/lib/pkgconfig ./configure --with-ssl

   Without pkg-config installed, use this:

        ./configure --with-ssl=/opt/OpenSSL

   provide the -R option to ld on some operating systems to set a hard-coded

   path to the run-time linker:

        LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl

        env LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl

   MORE OPTIONS

   ------------

     To build with GnuTLS support instead of OpenSSL for SSL/TLS, note that

     you need to use both --without-ssl and --with-gnutls.

     To build with yassl support instead of OpenSSL or GunTLS, you must build

     To build with yassl support instead of OpenSSL or GnuTLS, you must build

     yassl with its OpenSSL emulation enabled and point to that directory root

     with configure --with-ssl.

   The Open Watcom C compiler on Linux requires configuring with the variables:

     CC=owcc AR="$WATCOM/binl/wlib" AR_FLAGS=-q RANLIB=/bin/true \

     STRIP="$WATCOM/binl/wstrip" CFLAGS=-Wextra

       ./configure CC=owcc AR="$WATCOM/binl/wlib" AR_FLAGS=-q \

           RANLIB=/bin/true STRIP="$WATCOM/binl/wstrip" CFLAGS=-Wextra

Win32