1
Some hints about lftp compilation
2
---------------------------------
3
* invalid exception specifications in rltypedefs.h
4
Solution: use configure --with-included-readline or copy
5
readline-4.2/rlstdc.h and readline-4.2/tilde.h to your system include
6
directory /usr/include/readline.
7
* multiple declarations of rl_dispatching during linking
8
This is a bug in readline/readline.h header. Replace `int rl_dispatching'
9
with `extern int rl_dispatching' in /usr/include/readline/readline.h
10
Then do 'make clean; make' in lftp directory.
11
* g++ cannot create executables
12
You probably have not installed libstdc++ (or libg++). As a
13
workaround, you can try `CXX=gcc configure' to avoid linking with
15
* lftp cannot resolve host names
16
Try `configure --without-libresolv' - it can sometimes help.
17
* Sun C++ v5.0 compiler can be used to compile lftp. Use
18
CXX=CC CXXFLAGS="-compat=4 -features=bool" ./configure
19
* you need OpenSSL 0.9.5a or later to compile with SSL support.
26
These are generic installation instructions.
28
The `configure' shell script attempts to guess correct values for
29
various system-dependent variables used during compilation. It uses
30
those values to create a `Makefile' in each directory of the package.
31
It may also create one or more `.h' files containing system-dependent
32
definitions. Finally, it creates a shell script `config.status' that
33
you can run in the future to recreate the current configuration, a file
34
`config.cache' that saves the results of its tests to speed up
35
reconfiguring, and a file `config.log' containing compiler output
36
(useful mainly for debugging `configure').
38
If you need to do unusual things to compile the package, please try
39
to figure out how `configure' could check whether to do them, and mail
40
diffs or instructions to the address given in the `README' so they can
41
be considered for the next release. If at some point `config.cache'
42
contains results you don't want to keep, you may remove or edit it.
44
The file `configure.in' is used to create `configure' by a program
45
called `autoconf'. You only need `configure.in' if you want to change
46
it or regenerate `configure' using a newer version of `autoconf'.
48
The simplest way to compile this package is:
50
1. `cd' to the directory containing the package's source code and type
51
`./configure' to configure the package for your system. If you're
52
using `csh' on an old version of System V, you might need to type
53
`sh ./configure' instead to prevent `csh' from trying to execute
56
Running `configure' takes awhile. While running, it prints some
57
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
64
4. Type `make install' to install the programs and any data files and
67
5. You can remove the program binaries and object files from the
68
source code directory by typing `make clean'. To also remove the
69
files that `configure' created (so you can compile the package for
70
a different kind of computer), type `make distclean'. There is
71
also a `make maintainer-clean' target, but that is intended mainly
72
for the package's developers. If you use it, you may have to get
73
all sorts of other programs in order to regenerate files that came
74
with the distribution.
79
Some systems require unusual options for compilation or linking that
80
the `configure' script does not know about. You can give `configure'
81
initial values for variables by setting them in the environment. Using
82
a Bourne-compatible shell, you can do that on the command line like
84
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
86
Or on systems that have the `env' program, you can do it like this:
87
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
89
Compiling For Multiple Architectures
90
====================================
92
You can compile the package for more than one kind of computer at the
93
same time, by placing the object files for each architecture in their
94
own directory. To do this, you must use a version of `make' that
95
supports the `VPATH' variable, such as GNU `make'. `cd' to the
96
directory where you want the object files and executables to go and run
97
the `configure' script. `configure' automatically checks for the
98
source code in the directory that `configure' is in and in `..'.
100
If you have to use a `make' that does not supports the `VPATH'
101
variable, you have to compile the package for one architecture at a time
102
in the source code directory. After you have installed the package for
103
one architecture, use `make distclean' before reconfiguring for another
109
By default, `make install' will install the package's files in
110
`/usr/local/bin', `/usr/local/man', etc. You can specify an
111
installation prefix other than `/usr/local' by giving `configure' the
112
option `--prefix=PATH'.
114
You can specify separate installation prefixes for
115
architecture-specific files and architecture-independent files. If you
116
give `configure' the option `--exec-prefix=PATH', the package will use
117
PATH as the prefix for installing programs and libraries.
118
Documentation and other data files will still use the regular prefix.
120
In addition, if you use an unusual directory layout you can give
121
options like `--bindir=PATH' to specify different values for particular
122
kinds of files. Run `configure --help' for a list of the directories
123
you can set and what kinds of files go in them.
125
If the package supports it, you can cause programs to be installed
126
with an extra prefix or suffix on their names by giving `configure' the
127
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
132
Some packages pay attention to `--enable-FEATURE' options to
133
`configure', where FEATURE indicates an optional part of the package.
134
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
135
is something like `gnu-as' or `x' (for the X Window System). The
136
`README' should mention any `--enable-' and `--with-' options that the
139
For packages that use the X Window System, `configure' can usually
140
find the X include and library files automatically, but if it doesn't,
141
you can use the `configure' options `--x-includes=DIR' and
142
`--x-libraries=DIR' to specify their locations.
144
Specifying the System Type
145
==========================
147
There may be some features `configure' can not figure out
148
automatically, but needs to determine by the type of host the package
149
will run on. Usually `configure' can figure that out, but if it prints
150
a message saying it can not guess the host type, give it the
151
`--host=TYPE' option. TYPE can either be a short name for the system
152
type, such as `sun4', or a canonical name with three fields:
155
See the file `config.sub' for the possible values of each field. If
156
`config.sub' isn't included in this package, then this package doesn't
157
need to know the host type.
159
If you are building compiler tools for cross-compiling, you can also
160
use the `--target=TYPE' option to select the type of system they will
161
produce code for and the `--build=TYPE' option to select the type of
162
system on which you are compiling the package.
167
If you want to set default values for `configure' scripts to share,
168
you can create a site shell script called `config.site' that gives
169
default values for variables like `CC', `cache_file', and `prefix'.
170
`configure' looks for `PREFIX/share/config.site' if it exists, then
171
`PREFIX/etc/config.site' if it exists. Or, you can set the
172
`CONFIG_SITE' environment variable to the location of the site script.
173
A warning: not all `configure' scripts look for a site script.
178
`configure' recognizes the following options to control how it
182
Use and save the results of the tests in FILE instead of
183
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
184
debugging `configure'.
187
Print a summary of the options to `configure', and exit.
192
Do not print messages saying which checks are being made. To
193
suppress all normal output, redirect it to `/dev/null' (any error
194
messages will still be shown).
197
Look for the package's source code in directory DIR. Usually
198
`configure' can determine that directory automatically.
201
Print the version of Autoconf used to generate the `configure'
204
`configure' also accepts some other, not widely useful, options.
added
removed
INSTALL
