CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
`VPATH'variable, such as GNU
`make'. `cd'to the directory where you want the object files and executables to go and run the `configure' script.
`configure'automatically checks for the source code in the directory that `configure' is in and in `..'.
`VPATH'variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use
`make distclean'before reconfiguring for another architecture.
`/usr/local/man', etc. You can specify an installation prefix other than `/usr/local' by giving
`--exec-prefix=PATH', the package will use
PATHas the prefix for installing programs and libraries. Documentation and other data files will still use the regular prefix.
FEATUREindicates an optional part of the package. They may also pay attention to
PACKAGEis something like
`x'(for the X Window System). The `README' should mention any
`--with-'options that the package recognizes.
`--x-libraries=DIR'to specify their locations.
`configure'can not figure out automatically, but needs to determine by the type of host the package will run on. Usually `configure' can figure that out, but if it prints a message saying it can not guess the host type, give it the
`--host=TYPE'option. TYPE can either be a short name for the system type, such as
`sun4', or a canonical name with three fields:
`--target=TYPE'option to select the type of system they will produce code for and the
`--build=TYPE'option to select the type of system on which you are compiling the package.
`CC', `cache_file', and `prefix'.
`PREFIX/share/config.site'if it exists, then
`PREFIX/etc/config.site'if it exists. Or, you can set the
`CONFIG_SITE'environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script.
`configure'recognizes the following options to control how it operates.
|previous page | Top | next page|