123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255 |
- $Id: update-patches 24 2008-08-31 14:56:13Z wbx $
- --- libtirpc-0.2.0.orig/INSTALL 2009-05-28 21:25:26.000000000 +0200
- +++ libtirpc-0.2.0/INSTALL 2009-05-29 20:19:10.039164332 +0200
- @@ -1,35 +1,19 @@
- -Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
- -Foundation, Inc.
- +Installation Instructions
- +*************************
- +
- +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
- +2006, 2007, 2008 Free Software Foundation, Inc.
-
- This file is free documentation; the Free Software Foundation gives
- unlimited permission to copy, distribute and modify it.
-
- -
- -TI-RPC Library Quick Installation
- -=================================
- -
- - Without GSS API
- -
- -$ ./configure
- -$ make
- -# make install
- -
- - To enable utilization of RPCSEC via GSS API use following commands
- -but you need to install libgssapi from the CITI before
- -
- -$ ./configure --enable-gss
- -$ make
- -# make install
- -
- - Once installed, you can customize the /etc/netconfig configuration file
- -to configure the supported protocols. To support INET6 udp/tcp, uncomment
- -the udp6/tcp6 lines.
- -
- -
- Basic Installation
- ==================
-
- - These are generic installation instructions.
- + Briefly, the shell commands `./configure; make; make install' should
- +configure, build, and install this package. The following
- +more-detailed instructions are generic; see the `README' file for
- +instructions specific to this package.
-
- The `configure' shell script attempts to guess correct values for
- various system-dependent variables used during compilation. It uses
- @@ -42,9 +26,9 @@ debugging `configure').
-
- It can also use an optional file (typically called `config.cache'
- and enabled with `--cache-file=config.cache' or simply `-C') that saves
- -the results of its tests to speed up reconfiguring. (Caching is
- +the results of its tests to speed up reconfiguring. Caching is
- disabled by default to prevent problems with accidental use of stale
- -cache files.)
- +cache files.
-
- If you need to do unusual things to compile the package, please try
- to figure out how `configure' could check whether to do them, and mail
- @@ -54,20 +38,17 @@ some point `config.cache' contains resul
- may remove or edit it.
-
- The file `configure.ac' (or `configure.in') 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'.
- +`configure' by a program called `autoconf'. You 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:
-
- 1. `cd' to the directory containing the package's source code and type
- - `./configure' to configure the package for your system. If you're
- - using `csh' on an old version of System V, you might need to type
- - `sh ./configure' instead to prevent `csh' from trying to execute
- - `configure' itself.
- + `./configure' to configure the package for your system.
-
- - Running `configure' takes awhile. While running, it prints some
- - messages telling which features it is checking for.
- + Running `configure' might take a while. While running, it prints
- + some messages telling which features it is checking for.
-
- 2. Type `make' to compile the package.
-
- @@ -86,6 +67,9 @@ The simplest way to compile this package
- all sorts of other programs in order to regenerate files that came
- with the distribution.
-
- + 6. Often, you can also type `make uninstall' to remove the installed
- + files again.
- +
- Compilers and Options
- =====================
-
- @@ -97,7 +81,7 @@ for details on some of the pertinent env
- by setting variables in the command line or in the environment. Here
- is an example:
-
- - ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
- + ./configure CC=c99 CFLAGS=-g LIBS=-lposix
-
- *Note Defining Variables::, for more details.
-
- @@ -106,34 +90,46 @@ Compiling For Multiple Architectures
-
- You can compile the package for more than one kind of computer at the
- same time, by placing the object files for each architecture in their
- -own directory. To do this, you must use a version of `make' that
- -supports the `VPATH' variable, such as GNU `make'. `cd' to the
- +own directory. To do this, you can use 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 `..'.
-
- - If you have to use a `make' that does not support the `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.
- + With a non-GNU `make', it is safer 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.
- +
- + On MacOS X 10.5 and later systems, you can create libraries and
- +executables that work on multiple system types--known as "fat" or
- +"universal" binaries--by specifying multiple `-arch' options to the
- +compiler but only a single `-arch' option to the preprocessor. Like
- +this:
- +
- + ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
- + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
- + CPP="gcc -E" CXXCPP="g++ -E"
- +
- + This is not guaranteed to produce working output in all cases, you
- +may have to build one architecture at a time and combine the results
- +using the `lipo' tool if you have problems.
-
- Installation Names
- ==================
-
- - By default, `make install' will install the package's files in
- -`/usr/local/bin', `/usr/local/man', etc. You can specify an
- -installation prefix other than `/usr/local' by giving `configure' the
- -option `--prefix=PATH'.
- + By default, `make install' installs the package's commands under
- +`/usr/local/bin', include files under `/usr/local/include', etc. You
- +can specify an installation prefix other than `/usr/local' by giving
- +`configure' the option `--prefix=PREFIX'.
-
- You can specify separate installation prefixes for
- architecture-specific files and architecture-independent files. If you
- -give `configure' the option `--exec-prefix=PATH', the package will use
- -PATH as the prefix for installing programs and libraries.
- -Documentation and other data files will still use the regular prefix.
- +pass the option `--exec-prefix=PREFIX' to `configure', the package uses
- +PREFIX as the prefix for installing programs and libraries.
- +Documentation and other data files still use the regular prefix.
-
- In addition, if you use an unusual directory layout you can give
- -options like `--bindir=PATH' to specify different values for particular
- +options like `--bindir=DIR' to specify different values for particular
- kinds of files. Run `configure --help' for a list of the directories
- you can set and what kinds of files go in them.
-
- @@ -156,6 +152,28 @@ find the X include and library files aut
- you can use the `configure' options `--x-includes=DIR' and
- `--x-libraries=DIR' to specify their locations.
-
- +Particular systems
- +==================
- +
- + On HP-UX, the default C compiler is not ANSI C compatible. If GNU
- +CC is not installed, it is recommended to use the following options in
- +order to use an ANSI C compiler:
- +
- + ./configure CC="cc -Ae"
- +
- +and if that doesn't work, install pre-built binaries of GCC for HP-UX.
- +
- + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
- +parse its `<wchar.h>' 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"
- +
- Specifying the System Type
- ==========================
-
- @@ -178,7 +196,7 @@ where SYSTEM can have one of these forms
- need to know the machine type.
-
- If you are _building_ compiler tools for cross-compiling, you should
- -use the `--target=TYPE' option to select the type of system they will
- +use the option `--target=TYPE' to select the type of system they will
- produce code for.
-
- If you want to _use_ a cross compiler, that generates code for a
- @@ -208,9 +226,14 @@ them in the `configure' command line, us
-
- ./configure CC=/usr/local2/bin/gcc
-
- -will cause the specified gcc to be used as the C compiler (unless it is
- +causes the specified `gcc' to be used as the C compiler (unless it is
- overridden in the site shell script).
-
- +Unfortunately, this technique does not work for `CONFIG_SHELL' due to
- +an Autoconf bug. Until the bug is fixed you can use this workaround:
- +
- + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
- +
- `configure' Invocation
- ======================
-
- @@ -219,7 +242,14 @@ operates.
-
- `--help'
- `-h'
- - Print a summary of the options to `configure', and exit.
- + Print a summary of all of the options to `configure', and exit.
- +
- +`--help=short'
- +`--help=recursive'
- + Print a summary of the options unique to this package's
- + `configure', and exit. The `short' variant lists options used
- + only in the top level, while the `recursive' variant lists options
- + also present in any nested packages.
-
- `--version'
- `-V'
- @@ -246,6 +276,16 @@ operates.
- Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
-
- +`--prefix=DIR'
- + Use DIR as the installation prefix. *Note Installation Names::
- + for more details, including other options available for fine-tuning
- + the installation locations.
- +
- +`--no-create'
- +`-n'
- + Run the configure checks, but stop before creating any output
- + files.
- +
- `configure' also accepts some other, not widely useful, options. Run
- `configure --help' for more details.
-
|