From 3f87264c6ad4442932be56c8a0c18a688d6ca8f6 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Wed, 23 Aug 2006 17:22:58 +0000 Subject: Update from top-level directory. --- autoconf-lib-link/INSTALL | 27 ++++++++++++++++----------- gettext-runtime/INSTALL | 27 ++++++++++++++++----------- gettext-runtime/libasprintf/INSTALL | 27 ++++++++++++++++----------- gettext-tools/INSTALL | 27 ++++++++++++++++----------- 4 files changed, 64 insertions(+), 44 deletions(-) diff --git a/autoconf-lib-link/INSTALL b/autoconf-lib-link/INSTALL index 3c79932..e694669 100644 --- a/autoconf-lib-link/INSTALL +++ b/autoconf-lib-link/INSTALL @@ -19,8 +19,8 @@ diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. - The file `configure.in' is used to create `configure' by a program -called `autoconf'. You only need `configure.in' if you want to change + The file `configure.ac' is used to create `configure' by a program +called `autoconf'. You only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: @@ -56,13 +56,8 @@ 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 - -Or on systems that have the `env' program, you can do it like this: - env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure +initial values for variables as arguments. You can do it like this: + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix Compiling For Multiple Architectures ==================================== @@ -169,13 +164,23 @@ Particular Systems is not installed, it is recommended to use the following options in order to use an ANSI C compiler: - env CC="cc -Ae" ./configure + ./configure CC="cc -Ae" + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler don't grok +its header file. The option -nodtk can be used as a workaround. +If GNU CC is not installed, it is therefore recommended to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" On AIX 3, the C include files by default don't define some necessary prototype declarations. If GNU CC is not installed, it is recommended to use the following options: - env CC="xlc -D_ALL_SOURCE" ./configure + ./configure CC="xlc -D_ALL_SOURCE" On BeOS, user installed software goes in /boot/home/config, not /usr/local. It is recommended to use the following options: diff --git a/gettext-runtime/INSTALL b/gettext-runtime/INSTALL index 3c79932..e694669 100644 --- a/gettext-runtime/INSTALL +++ b/gettext-runtime/INSTALL @@ -19,8 +19,8 @@ diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. - The file `configure.in' is used to create `configure' by a program -called `autoconf'. You only need `configure.in' if you want to change + The file `configure.ac' is used to create `configure' by a program +called `autoconf'. You only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: @@ -56,13 +56,8 @@ 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 - -Or on systems that have the `env' program, you can do it like this: - env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure +initial values for variables as arguments. You can do it like this: + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix Compiling For Multiple Architectures ==================================== @@ -169,13 +164,23 @@ Particular Systems is not installed, it is recommended to use the following options in order to use an ANSI C compiler: - env CC="cc -Ae" ./configure + ./configure CC="cc -Ae" + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler don't grok +its header file. The option -nodtk can be used as a workaround. +If GNU CC is not installed, it is therefore recommended to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" On AIX 3, the C include files by default don't define some necessary prototype declarations. If GNU CC is not installed, it is recommended to use the following options: - env CC="xlc -D_ALL_SOURCE" ./configure + ./configure CC="xlc -D_ALL_SOURCE" On BeOS, user installed software goes in /boot/home/config, not /usr/local. It is recommended to use the following options: diff --git a/gettext-runtime/libasprintf/INSTALL b/gettext-runtime/libasprintf/INSTALL index 3c79932..e694669 100644 --- a/gettext-runtime/libasprintf/INSTALL +++ b/gettext-runtime/libasprintf/INSTALL @@ -19,8 +19,8 @@ diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. - The file `configure.in' is used to create `configure' by a program -called `autoconf'. You only need `configure.in' if you want to change + The file `configure.ac' is used to create `configure' by a program +called `autoconf'. You only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: @@ -56,13 +56,8 @@ 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 - -Or on systems that have the `env' program, you can do it like this: - env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure +initial values for variables as arguments. You can do it like this: + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix Compiling For Multiple Architectures ==================================== @@ -169,13 +164,23 @@ Particular Systems is not installed, it is recommended to use the following options in order to use an ANSI C compiler: - env CC="cc -Ae" ./configure + ./configure CC="cc -Ae" + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler don't grok +its header file. The option -nodtk can be used as a workaround. +If GNU CC is not installed, it is therefore recommended to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" On AIX 3, the C include files by default don't define some necessary prototype declarations. If GNU CC is not installed, it is recommended to use the following options: - env CC="xlc -D_ALL_SOURCE" ./configure + ./configure CC="xlc -D_ALL_SOURCE" On BeOS, user installed software goes in /boot/home/config, not /usr/local. It is recommended to use the following options: diff --git a/gettext-tools/INSTALL b/gettext-tools/INSTALL index 3c79932..e694669 100644 --- a/gettext-tools/INSTALL +++ b/gettext-tools/INSTALL @@ -19,8 +19,8 @@ diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. - The file `configure.in' is used to create `configure' by a program -called `autoconf'. You only need `configure.in' if you want to change + The file `configure.ac' is used to create `configure' by a program +called `autoconf'. You only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: @@ -56,13 +56,8 @@ 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 - -Or on systems that have the `env' program, you can do it like this: - env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure +initial values for variables as arguments. You can do it like this: + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix Compiling For Multiple Architectures ==================================== @@ -169,13 +164,23 @@ Particular Systems is not installed, it is recommended to use the following options in order to use an ANSI C compiler: - env CC="cc -Ae" ./configure + ./configure CC="cc -Ae" + + On OSF/1 a.k.a. Tru64, some versions of the default C compiler don't grok +its header file. The option -nodtk can be used as a workaround. +If GNU CC is not installed, it is therefore recommended to try + + ./configure CC="cc" + +and if that doesn't work, try + + ./configure CC="cc -nodtk" On AIX 3, the C include files by default don't define some necessary prototype declarations. If GNU CC is not installed, it is recommended to use the following options: - env CC="xlc -D_ALL_SOURCE" ./configure + ./configure CC="xlc -D_ALL_SOURCE" On BeOS, user installed software goes in /boot/home/config, not /usr/local. It is recommended to use the following options: -- cgit v1.1