-
-So, if you want to configure Wget for installation in your home
-directory, you can type:
-./configure --prefix=$HOME
-
-You can customize many default settings by editing Makefile and
-config.h. The program will work very well without your touching these
-files, but it is useful to have a look at things you can change there.
-
-If you use socks, it is useful to add -L/usr/local/lib (or wherever
-the socks library is installed) to LDFLAGS in Makefile.
-
-If you have OpenSSL installed in its default /usr/local/ssl directory
-(i.e. libraries are in /usr/local/ssl/lib), you can simply
-`configure --with-ssl'. If you have it installed elsewhere, you need
-to specify your alternate OpenSSL root directory. For instance, if
-libcrypto.* and libssl.* are in /usr/local/lib, you need to
-`configure --with-ssl=/usr/local'.
-
-To configure Wget on Windows, run configure.bat and follow the
-instructions in the windows/ directory. If this doesn't work for any
-reason, talk to the Windows developers listed in `windows/README'; I
-do not maintain the port.
-
-2) Compilation
-
-To compile the program, type make and cross your fingers. If you do
-not have an ANSI compiler, Wget will try to KNR-ize its sources "on
-the fly". This should make GNU Wget compilable virtually anywhere.
-
-After the compilation a ready to use `wget' executable should reside
-in the src directory. I do not have any kind of test-suite as of this
-moment, but it should be easy enough to test whether the basic stuff
-works.
-
-3) Installation
+ --disable-largefile omit support for large files
+ --disable-ipv6 disable IPv6 support
+ --disable-rpath do not hardcode runtime library paths
+
+You can inspect decisions made by configure by editing the generated
+Makefiles and the `src/config.h' include file. The defaults should
+work without intervention, but if you know what you are doing, editing
+the generated files before compilation is fine -- they will not be
+regenerated until you run configure again.
+
+`configure' will try to find a compiler in your PATH, defaulting to
+`gcc', but falling back to `cc' if the former is unavailable. This is
+a reasonable default on most Unix-like systems, but sometimes you
+might want to override it. The compiler choice is overridden by
+setting the `CC' environment variable to the desired compiler file
+name. For example, to force compilation with the Unix `cc' compiler,
+invoke configure like this:
+
+ ./configure CC=cc
+
+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 the use of --without-* flags, configure will try to autodetect
+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. This often happens on GNU/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 believe you have the necessary
+headers, but configure still fails to detect the library, please
+report it as a bug.
+
+3. Compilation
+--------------
+
+To compile GNU Wget after it has been configured, simply type make.
+Wget requires a compiler and standard library compliant with the 1990
+ISO C standard, which includes the vast majority of compilation
+environments present on systems in use today.
+
+After the compilation a ready-to-use `wget' executable should reside
+in the src directory. At this point there is no formal test suite for
+testing the binary, but it should be easy enough to test whether the
+basic functionality works.
+
+4. Installation
+---------------