-This assumes that `cc' is in your path -- if it is not, simply replace
-"cc" with "/path/to/cc". Note that environment variables that affect
-configure can be set with the usual shell syntax `var=value
-./configure' (assuming an sh-compatible shell). In addition to that,
-configure allows environment variables to be specified as arguments in
-the form "var=value", which are shell-independent.
-
-Environment variables that affect `configure' include: CFLAGS for
-compilation flags, LDFLAGS for linker flags, and CPPFLAGS for
-preprocessor flags.
-
-If you have OpenSSL libraries installed at one of the default
-locations, such as the system library directories or /usr/local/lib or
-/usr/local/ssl/lib, configure will autodetect them. If they are
-installed elsewhere, you need to specify the OpenSSL root directory.
-For instance, if libcrypto.* and libssl.* are in /opt/openssl/lib, you
-need to `configure --with-ssl=/opt/openssl'.
-
-To configure Wget on Windows, read the instructions in
-`windows/README'. If this doesn't work for any reason, talk to the
-Windows developers listed there; I do not maintain the port. Those
-instructions do not apply to the "Cygwin" environment, where Wget
-should build out of the box as described here.
-
-2) Compilation
+This assumes that `cc' is in your path -- if it is not, simply use
+CC=/path/to/cc instead. Note that environment variables that affect
+configure can be set with the usual shell syntax `VAR=value
+./configure' (assuming sh syntax), but can also be specified as
+arguments to configure, as shown above. The latter method, while
+being specific to configure, works unmodified in all shells.
+
+Environment variables that affect `configure' include: CFLAGS for C
+compiler flags, CPPFLAGS for C preprocessor flags, LDFLAGS for linker
+flags, and LIBS for libraries.
+
+Barring a the use of --without-* flags, configure will try to
+autodetect certain external libraries needed by Wget, currently only
+the OpenSSL libraries. If they are installed in the system library
+directories or in the same prefix where you plan to install Wget,
+configure should be able to autodetect them. If they are installed
+elsewhere, use the `--with-libNAME' option to specify the root
+directory under which libraries reside in the `lib/' subdirectory and
+the corresponding header files reside in the `include/' subdirectory.
+For example, if the OpenSSL libraries are installed under the
+/usr/local/ssl prefix, use `--with-libssl=/usr/local/ssl'.
+
+Sometimes external libraries will be installed on the system, but the
+header files will be missing, which happens on Linux if you forget to
+install the "-devel" or "-dev" package that corresponds to the library
+and that is typically *not* installed by default. In that case
+configure will not find the library and you will not be able to use
+the features provided by the library until you install the devel
+package and rerun configure. If you have all the necessary headers,
+but configure still fails to detect the library, report a bug.
+
+2. Compilation
+--------------