From: Ben Elliston Date: Tue, 26 Oct 1999 03:54:59 +0000 (+0000) Subject: * merged from the experimental branch. X-Git-Tag: post-exp-merge-1999-10-31~4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c4245421c879837cebaca95bc491b6611e4b2832;p=thirdparty%2Fautoconf.git * merged from the experimental branch. 1999-10-26 Ben Elliston * INSTALL: Regenerate. 1999-09-22 Akim Demaille * install.texi: Give more details on envvar handling. --- diff --git a/INSTALL b/INSTALL index 50dbe439..942c83bb 100644 --- a/INSTALL +++ b/INSTALL @@ -55,14 +55,14 @@ Compilers and Options ===================== Some systems require unusual options for compilation or linking that -the `configure' script does not know about. You can give `configure' -initial values for variables by setting them in the environment. Using -a Bourne-compatible shell, you can do that on the command line like -this: - CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure +the `configure' script does not know about. Run `./configure --help' +for details on some of the pertinent environment variables. + + You can give `configure' initial values for variables by setting +them in the environment. You can do that on the command line like this: + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix -Or on systems that have the `env' program, you can do it like this: - env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure + *Note Environment Variables::, for more details. Compiling For Multiple Architectures ==================================== @@ -122,10 +122,10 @@ you can use the `configure' options `--x-includes=DIR' and Specifying the System Type ========================== - There may be some features `configure' can not figure out + There may be some features `configure' cannot 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 +a message saying it cannot 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: CPU-COMPANY-SYSTEM @@ -150,6 +150,24 @@ default values for variables like `CC', `cache_file', and `prefix'. `CONFIG_SITE' environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script. +Environment Variables +===================== + + Variables not defined in a site shell script can be set in the +environment passed to configure. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the `configure' command line, using `VAR=value'. For example: + ./configure CC=/usr/local2/bin/gcc + will cause the specified gcc to be used as the C compiler (unless it +is overridden in the site shell script). + + Please, note that the former interface: + CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure + or + env CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure + should be avoided. + Operation Controls ================== diff --git a/doc/install.texi b/doc/install.texi index f38a8fc5..7b7119ec 100644 --- a/doc/install.texi +++ b/doc/install.texi @@ -67,21 +67,19 @@ other programs in order to regenerate files that came with the distribution. @node Compilers and Options @section Compilers and Options -Some systems require unusual options for compilation or linking that -the @code{configure} script does not know about. You can give -@code{configure} initial values for variables by setting them in the -environment. Using a Bourne-compatible shell, you can do that on the -command line like this: -@example -CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure -@end example +Some systems require unusual options for compilation or linking that the +@code{configure} script does not know about. Run @samp{./configure +--help} for details on some of the pertinent environment variables. -@noindent -Or on systems that have the @code{env} program, you can do it like this: +You can give @code{configure} initial values for variables by setting +them in the environment. You can do that on the command line like this: @example -env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure +./configure CC=c89 CFLAGS=-O2 LIBS=-lposix @end example +@xref{Environment Variables}, for more details. + + @node Multiple Architectures @section Compiling For Multiple Architectures @@ -174,6 +172,32 @@ default values for variables like @code{CC}, @code{cache_file}, and the @code{CONFIG_SITE} environment variable to the location of the site script. A warning: not all @code{configure} scripts look for a site script. +@node Environment Variables +@section Environment Variables + +Variables not defined in a site shell script can be set in the +environment passed to configure. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the @code{configure} command line, using @samp{VAR=value}. For +example: +@example +./configure CC=/usr/local2/bin/gcc +@end example +will cause the specified gcc to be used as the C compiler (unless it is +overridden in the site shell script). + +Please, note that the former interface: +@example +CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure +@end example +or +@example +env CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure +@end example +should be avoided. + + @node Operation Controls @section Operation Controls diff --git a/install.texi b/install.texi index f38a8fc5..7b7119ec 100644 --- a/install.texi +++ b/install.texi @@ -67,21 +67,19 @@ other programs in order to regenerate files that came with the distribution. @node Compilers and Options @section Compilers and Options -Some systems require unusual options for compilation or linking that -the @code{configure} script does not know about. You can give -@code{configure} initial values for variables by setting them in the -environment. Using a Bourne-compatible shell, you can do that on the -command line like this: -@example -CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure -@end example +Some systems require unusual options for compilation or linking that the +@code{configure} script does not know about. Run @samp{./configure +--help} for details on some of the pertinent environment variables. -@noindent -Or on systems that have the @code{env} program, you can do it like this: +You can give @code{configure} initial values for variables by setting +them in the environment. You can do that on the command line like this: @example -env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure +./configure CC=c89 CFLAGS=-O2 LIBS=-lposix @end example +@xref{Environment Variables}, for more details. + + @node Multiple Architectures @section Compiling For Multiple Architectures @@ -174,6 +172,32 @@ default values for variables like @code{CC}, @code{cache_file}, and the @code{CONFIG_SITE} environment variable to the location of the site script. A warning: not all @code{configure} scripts look for a site script. +@node Environment Variables +@section Environment Variables + +Variables not defined in a site shell script can be set in the +environment passed to configure. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the @code{configure} command line, using @samp{VAR=value}. For +example: +@example +./configure CC=/usr/local2/bin/gcc +@end example +will cause the specified gcc to be used as the C compiler (unless it is +overridden in the site shell script). + +Please, note that the former interface: +@example +CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure +@end example +or +@example +env CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure +@end example +should be avoided. + + @node Operation Controls @section Operation Controls