2
GNU Wget Installation Procedure
3
===============================
8
This document describes how to build Wget from source code on
9
Unix-like systems. If you want to install a precompiled Wget, this
10
document is not for you -- refer to the documentation provided by the
11
distributors instead. If you already have Wget and want to learn how
12
to use it, refer to Wget's Info documentation or man page which you
13
should have received with your system. If you are using Windows
14
(except for Cygwin), read windows/README instead. If you want to
15
compile Wget from source code on a Unix-like system, read on.
17
The preferred form of building Wget is to get a release archive and
18
unpack it (which you have presumably done, since you are reading
19
this). If you have obtained the source code via the Mercurial
20
repository, please follow the instructions in `README.checkout' before
21
continuing, as the sources from the Mercurial repository do not include
22
some files that are present in official distributions; these additional
23
files must be generated first.
28
To build Wget, your system must support a Unix-like command-line
29
development environment, including the text-processing utilities (sh,
30
grep, awk, sed, etc.) and a functional C compiler. On some GNU/Linux
31
systems, this means that you will need to install packages such as
32
`gcc', `glibc-devel' (or `libc6-dev') and `make'. Most systems come
33
with these packages preinstalled, but it doesn't hurt to check. If
34
you have successfully compiled other software from source, you
35
probably have them all.
37
In addition to the C development environment, Wget can use a number of
38
optional libraries to provide additional features, such as translated
39
messages and support for "https" URLs. The "external" dependencies
42
- OpenSSL -- for "https" URLs.
43
- GNU gettext -- for translated messages.
44
- GNU libidn -- for IDN/IRI support.
45
- GNU libiconv -- for IDN/IRI support (not needed on GNU).
47
To be usable for building Wget, the listed libraries must be installed
48
with their "development" header files. On GNU/Linux systems this
49
typically means installing the corredponsing "lib<name>-devel" or
50
"lib<name>-dev" package along with the package with "lib<name>".
55
Before compiling Wget, you need to "configure" it using the
56
`configure' script provided with the distribution. Configuration
57
serves two distinct purposes: it enables Wget's build system to
58
inspect certain features of your operating system for more robust
59
compilation, and it enables you to choose which features you want the
60
resulting Wget to have.
62
As is the case with most GNU software, Wget's configure script was
63
generated with GNU Autoconf. If you're not familiar with
64
Autoconf-generated scripts, read on.
66
The most straightforward way to configure Wget is by running the
67
configure script without any arguments. After running some
68
compilation-related tests, it will create the Makefiles needed to
69
build Wget. However, you may wish to customize Wget's configuration
70
by providing arguments to `configure'. Wget's configure script
71
accepts standard Autoconf arguments, the most important ones being:
73
--help display a help message and exit
75
--prefix=PREFIX install architecture-independent files in PREFIX
76
(/usr/local by default)
77
--bindir=DIR user executables in DIR (PREFIX/bin)
78
--infodir=DIR info documentation in DIR [PREFIX/info]
79
--mandir=DIR man documentation in DIR [PREFIX/man]
81
For example, if you are not root and want to install Wget in
82
subdirectories of your home directory, you can use:
84
./configure --prefix=$HOME
86
In addition to the above generic options, Wget's configuration
87
supports a number of options more or less specific to Wget. Options
88
beginning with "--disable", such as `--disable-opie' or
89
`--disable-ntlm', allow you to turn off certain built-in functionality
90
you don't need in order to reduce the size of the executable. Options
91
beginning with "--with" turning off autodetection and use of external
92
software Wget can link with, such as the SSL libraries. Recognized
93
"--enable" and "--with" options include:
95
--without-ssl disable SSL autodetection (used for https support)
96
--with-libssl-prefix=DIR search for libssl in DIR/lib
97
--disable-opie disable support for opie or s/key FTP login
98
--disable-digest disable support for HTTP digest authorization
99
--disable-ntlm disable support for HTTP NTLM authorization
100
--disable-debug disable support for debugging output
101
--disable-nls do not use Native Language Support
102
--disable-largefile omit support for large files
103
--disable-ipv6 disable IPv6 support
104
--disable-rpath do not hardcode runtime library paths
105
--disable-iri disable IDN/IRIs support
107
For the full list, see the output of `./configure --help'.
109
You can inspect decisions made by configure by editing the generated
110
Makefiles and the `src/config.h' include file. The defaults should
111
work without intervention, but if you know what you are doing, editing
112
the generated files before compilation is fine -- they will not be
113
regenerated until you run configure again.
115
`configure' will try to find a compiler in your PATH, defaulting to
116
`gcc', but falling back to `cc' if the former is unavailable. This is
117
a reasonable default on most Unix-like systems, but sometimes you
118
might want to override it. The compiler choice is overridden by
119
setting the `CC' environment variable to the desired compiler file
120
name. For example, to force compilation with the Unix `cc' compiler,
121
invoke configure like this:
125
This assumes that `cc' is in your path -- if it is not, simply use
126
CC=/path/to/cc instead. Note that environment variables that affect
127
configure can be set with the usual shell syntax `VAR=value ./configure'
128
(assuming sh syntax), but can also be specified as arguments to
129
configure, as shown above. The latter method, while being specific to
130
configure, works unmodified in all shells, and in addition allows
131
configure to detect when that setting has been changed across
134
Environment variables that affect `configure' include: CFLAGS for C
135
compiler flags, CPPFLAGS for C preprocessor flags, LDFLAGS for linker
136
flags, and LIBS for libraries.
138
Barring the use of --without-* flags, configure will try to autodetect
139
external libraries needed by Wget, currently only the OpenSSL
140
libraries. If they are installed in the system library directories or
141
in the same prefix where you plan to install Wget, configure should be
142
able to autodetect them. If they are installed elsewhere, use the
143
`--with-libNAME' option to specify the root directory under which
144
libraries reside in the `lib/' subdirectory and the corresponding
145
header files reside in the `include/' subdirectory. For example, if
146
the OpenSSL libraries are installed under the /usr/local/ssl prefix,
147
use `--with-libssl=/usr/local/ssl'.
149
Sometimes external libraries will be installed on the system, but the
150
header files will be missing. This often happens on GNU/Linux if you
151
forget to install the "-devel" or "-dev" package that corresponds to
152
the library and that is typically *not* installed by default. In that
153
case configure will not find the library and you will not be able to
154
use the features provided by the library until you install the devel
155
package and rerun configure. If you believe you have the necessary
156
headers, but configure still fails to detect the library, please
162
To compile GNU Wget after it has been configured, simply type make.
163
Wget requires a compiler and standard library compliant with the 1990
164
ISO C standard, which includes the vast majority of compilation
165
environments present on systems in use today.
167
After the compilation a ready-to-use `wget' executable should reside
168
in the src directory. At this point there is no formal test suite for
169
testing the binary, but it should be easy enough to test whether the
170
basic functionality works.
175
Use `make install' to install GNU Wget to directories specified to
176
configure. To install it in a system directory (which is the
177
default), you will need to be root. The standard prefix is
178
"/usr/local/", which can be changed using the `--prefix' configure
181
The installation process will copy the wget binary to $PREFIX/bin,
182
install the wget.info* info pages to $PREFIX/info, the generated
183
manual page (where available) wget.1 to $PREFIX/man/man1, and the
184
default config file to $PREFIX/etc, unless a config file already
185
exists there. You can customize these directories either through the
186
configuration process or making the necessary changes in the Makefile.
188
To delete the files created by Wget installation, you can use `make
1
Installation Instructions
2
*************************
4
Copyright (C) 1994-1996, 1999-2002, 2004-2011 Free Software Foundation,
7
Copying and distribution of this file, with or without modification,
8
are permitted in any medium without royalty provided the copyright
9
notice and this notice are preserved. This file is offered as-is,
10
without warranty of any kind.
15
Briefly, the shell commands `./configure; make; make install' should
16
configure, build, and install this package. The following
17
more-detailed instructions are generic; see the `README' file for
18
instructions specific to this package. Some packages provide this
19
`INSTALL' file but do not implement all of the features documented
20
below. The lack of an optional feature in a given package is not
21
necessarily a bug. More recommendations for GNU packages can be found
22
in *note Makefile Conventions: (standards)Makefile Conventions.
24
The `configure' shell script attempts to guess correct values for
25
various system-dependent variables used during compilation. It uses
26
those values to create a `Makefile' in each directory of the package.
27
It may also create one or more `.h' files containing system-dependent
28
definitions. Finally, it creates a shell script `config.status' that
29
you can run in the future to recreate the current configuration, and a
30
file `config.log' containing compiler output (useful mainly for
31
debugging `configure').
33
It can also use an optional file (typically called `config.cache'
34
and enabled with `--cache-file=config.cache' or simply `-C') that saves
35
the results of its tests to speed up reconfiguring. Caching is
36
disabled by default to prevent problems with accidental use of stale
39
If you need to do unusual things to compile the package, please try
40
to figure out how `configure' could check whether to do them, and mail
41
diffs or instructions to the address given in the `README' so they can
42
be considered for the next release. If you are using the cache, and at
43
some point `config.cache' contains results you don't want to keep, you
44
may remove or edit it.
46
The file `configure.ac' (or `configure.in') is used to create
47
`configure' by a program called `autoconf'. You need `configure.ac' if
48
you want to change it or regenerate `configure' using a newer version
51
The simplest way to compile this package is:
53
1. `cd' to the directory containing the package's source code and type
54
`./configure' to configure the package for your system.
56
Running `configure' might take a while. While running, it prints
57
some messages telling which features it is checking for.
59
2. Type `make' to compile the package.
61
3. Optionally, type `make check' to run any self-tests that come with
62
the package, generally using the just-built uninstalled binaries.
64
4. Type `make install' to install the programs and any data files and
65
documentation. When installing into a prefix owned by root, it is
66
recommended that the package be configured and built as a regular
67
user, and only the `make install' phase executed with root
70
5. Optionally, type `make installcheck' to repeat any self-tests, but
71
this time using the binaries in their final installed location.
72
This target does not install anything. Running this target as a
73
regular user, particularly if the prior `make install' required
74
root privileges, verifies that the installation completed
77
6. You can remove the program binaries and object files from the
78
source code directory by typing `make clean'. To also remove the
79
files that `configure' created (so you can compile the package for
80
a different kind of computer), type `make distclean'. There is
81
also a `make maintainer-clean' target, but that is intended mainly
82
for the package's developers. If you use it, you may have to get
83
all sorts of other programs in order to regenerate files that came
84
with the distribution.
86
7. Often, you can also type `make uninstall' to remove the installed
87
files again. In practice, not all packages have tested that
88
uninstallation works correctly, even though it is required by the
91
8. Some packages, particularly those that use Automake, provide `make
92
distcheck', which can by used by developers to test that all other
93
targets like `make install' and `make uninstall' work correctly.
94
This target is generally not run by end users.
99
Some systems require unusual options for compilation or linking that
100
the `configure' script does not know about. Run `./configure --help'
101
for details on some of the pertinent environment variables.
103
You can give `configure' initial values for configuration parameters
104
by setting variables in the command line or in the environment. Here
107
./configure CC=c99 CFLAGS=-g LIBS=-lposix
109
*Note Defining Variables::, for more details.
111
Compiling For Multiple Architectures
112
====================================
114
You can compile the package for more than one kind of computer at the
115
same time, by placing the object files for each architecture in their
116
own directory. To do this, you can use GNU `make'. `cd' to the
117
directory where you want the object files and executables to go and run
118
the `configure' script. `configure' automatically checks for the
119
source code in the directory that `configure' is in and in `..'. This
120
is known as a "VPATH" build.
122
With a non-GNU `make', it is safer to compile the package for one
123
architecture at a time in the source code directory. After you have
124
installed the package for one architecture, use `make distclean' before
125
reconfiguring for another architecture.
127
On MacOS X 10.5 and later systems, you can create libraries and
128
executables that work on multiple system types--known as "fat" or
129
"universal" binaries--by specifying multiple `-arch' options to the
130
compiler but only a single `-arch' option to the preprocessor. Like
133
./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
134
CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
135
CPP="gcc -E" CXXCPP="g++ -E"
137
This is not guaranteed to produce working output in all cases, you
138
may have to build one architecture at a time and combine the results
139
using the `lipo' tool if you have problems.
144
By default, `make install' installs the package's commands under
145
`/usr/local/bin', include files under `/usr/local/include', etc. You
146
can specify an installation prefix other than `/usr/local' by giving
147
`configure' the option `--prefix=PREFIX', where PREFIX must be an
150
You can specify separate installation prefixes for
151
architecture-specific files and architecture-independent files. If you
152
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
153
PREFIX as the prefix for installing programs and libraries.
154
Documentation and other data files still use the regular prefix.
156
In addition, if you use an unusual directory layout you can give
157
options like `--bindir=DIR' to specify different values for particular
158
kinds of files. Run `configure --help' for a list of the directories
159
you can set and what kinds of files go in them. In general, the
160
default for these options is expressed in terms of `${prefix}', so that
161
specifying just `--prefix' will affect all of the other directory
162
specifications that were not explicitly provided.
164
The most portable way to affect installation locations is to pass the
165
correct locations to `configure'; however, many packages provide one or
166
both of the following shortcuts of passing variable assignments to the
167
`make install' command line to change installation locations without
168
having to reconfigure or recompile.
170
The first method involves providing an override variable for each
171
affected directory. For example, `make install
172
prefix=/alternate/directory' will choose an alternate location for all
173
directory configuration variables that were expressed in terms of
174
`${prefix}'. Any directories that were specified during `configure',
175
but not in terms of `${prefix}', must each be overridden at install
176
time for the entire installation to be relocated. The approach of
177
makefile variable overrides for each directory variable is required by
178
the GNU Coding Standards, and ideally causes no recompilation.
179
However, some platforms have known limitations with the semantics of
180
shared libraries that end up requiring recompilation when using this
181
method, particularly noticeable in packages that use GNU Libtool.
183
The second method involves providing the `DESTDIR' variable. For
184
example, `make install DESTDIR=/alternate/directory' will prepend
185
`/alternate/directory' before all installation names. The approach of
186
`DESTDIR' overrides is not required by the GNU Coding Standards, and
187
does not work on platforms that have drive letters. On the other hand,
188
it does better at avoiding recompilation issues, and works well even
189
when some directory options were not specified in terms of `${prefix}'
195
If the package supports it, you can cause programs to be installed
196
with an extra prefix or suffix on their names by giving `configure' the
197
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
199
Some packages pay attention to `--enable-FEATURE' options to
200
`configure', where FEATURE indicates an optional part of the package.
201
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
202
is something like `gnu-as' or `x' (for the X Window System). The
203
`README' should mention any `--enable-' and `--with-' options that the
206
For packages that use the X Window System, `configure' can usually
207
find the X include and library files automatically, but if it doesn't,
208
you can use the `configure' options `--x-includes=DIR' and
209
`--x-libraries=DIR' to specify their locations.
211
Some packages offer the ability to configure how verbose the
212
execution of `make' will be. For these packages, running `./configure
213
--enable-silent-rules' sets the default to minimal output, which can be
214
overridden with `make V=1'; while running `./configure
215
--disable-silent-rules' sets the default to verbose, which can be
216
overridden with `make V=0'.
221
On HP-UX, the default C compiler is not ANSI C compatible. If GNU
222
CC is not installed, it is recommended to use the following options in
223
order to use an ANSI C compiler:
225
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
227
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
229
HP-UX `make' updates targets which have the same time stamps as
230
their prerequisites, which makes it generally unusable when shipped
231
generated files such as `configure' are involved. Use GNU `make'
234
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
235
parse its `<wchar.h>' header file. The option `-nodtk' can be used as
236
a workaround. If GNU CC is not installed, it is therefore recommended
241
and if that doesn't work, try
243
./configure CC="cc -nodtk"
245
On Solaris, don't put `/usr/ucb' early in your `PATH'. This
246
directory contains several dysfunctional programs; working variants of
247
these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
248
in your `PATH', put it _after_ `/usr/bin'.
250
On Haiku, software installed for all users goes in `/boot/common',
251
not `/usr/local'. It is recommended to use the following options:
253
./configure --prefix=/boot/common
255
Specifying the System Type
256
==========================
258
There may be some features `configure' cannot figure out
259
automatically, but needs to determine by the type of machine the package
260
will run on. Usually, assuming the package is built to be run on the
261
_same_ architectures, `configure' can figure that out, but if it prints
262
a message saying it cannot guess the machine type, give it the
263
`--build=TYPE' option. TYPE can either be a short name for the system
264
type, such as `sun4', or a canonical name which has the form:
268
where SYSTEM can have one of these forms:
273
See the file `config.sub' for the possible values of each field. If
274
`config.sub' isn't included in this package, then this package doesn't
275
need to know the machine type.
277
If you are _building_ compiler tools for cross-compiling, you should
278
use the option `--target=TYPE' to select the type of system they will
281
If you want to _use_ a cross compiler, that generates code for a
282
platform different from the build platform, you should specify the
283
"host" platform (i.e., that on which the generated programs will
284
eventually be run) with `--host=TYPE'.
289
If you want to set default values for `configure' scripts to share,
290
you can create a site shell script called `config.site' that gives
291
default values for variables like `CC', `cache_file', and `prefix'.
292
`configure' looks for `PREFIX/share/config.site' if it exists, then
293
`PREFIX/etc/config.site' if it exists. Or, you can set the
294
`CONFIG_SITE' environment variable to the location of the site script.
295
A warning: not all `configure' scripts look for a site script.
300
Variables not defined in a site shell script can be set in the
301
environment passed to `configure'. However, some packages may run
302
configure again during the build, and the customized values of these
303
variables may be lost. In order to avoid this problem, you should set
304
them in the `configure' command line, using `VAR=value'. For example:
306
./configure CC=/usr/local2/bin/gcc
308
causes the specified `gcc' to be used as the C compiler (unless it is
309
overridden in the site shell script).
311
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
312
an Autoconf bug. Until the bug is fixed you can use this workaround:
314
CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
316
`configure' Invocation
317
======================
319
`configure' recognizes the following options to control how it
324
Print a summary of all of the options to `configure', and exit.
328
Print a summary of the options unique to this package's
329
`configure', and exit. The `short' variant lists options used
330
only in the top level, while the `recursive' variant lists options
331
also present in any nested packages.
335
Print the version of Autoconf used to generate the `configure'
339
Enable the cache: use and save the results of the tests in FILE,
340
traditionally `config.cache'. FILE defaults to `/dev/null' to
345
Alias for `--cache-file=config.cache'.
350
Do not print messages saying which checks are being made. To
351
suppress all normal output, redirect it to `/dev/null' (any error
352
messages will still be shown).
355
Look for the package's source code in directory DIR. Usually
356
`configure' can determine that directory automatically.
359
Use DIR as the installation prefix. *note Installation Names::
360
for more details, including other options available for fine-tuning
361
the installation locations.
365
Run the configure checks, but stop before creating any output
368
`configure' also accepts some other, not widely useful, options. Run
369
`configure --help' for more details.
added
removed
INSTALL
