Changeset 280 in kBuild for branches/GNU/src/gmake/INSTALL
- Timestamp:
- May 16, 2005 4:54:02 PM (19 years ago)
- Location:
- branches/GNU/src/gmake
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/GNU/src/gmake
- Property svn:ignore
-
old new 34 34 README.DOS 35 35 README.W32 36 README.OS2 36 37 aclocal.m4 37 38 autom4te.cache
-
- Property svn:ignore
-
branches/GNU/src/gmake/INSTALL
r153 r280 1 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software 2 Foundation, Inc. 3 4 This file is free documentation; the Free Software Foundation gives 1 Installation Instructions 2 ************************* 3 4 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free 5 Software Foundation, Inc. 6 7 This file is free documentation; the Free Software Foundation gives 5 8 unlimited permission to copy, distribute and modify it. 6 9 … … 8 11 ================== 9 12 10 These are generic installation instructions.13 These are generic installation instructions. 11 14 12 15 The `configure' shell script attempts to guess correct values for … … 68 71 ===================== 69 72 70 Some systems require unusual options for compilation or linking that 71 the `configure' script does not know about. Run `./configure --help' 72 fordetails on some of the pertinent environment variables.73 Some systems require unusual options for compilation or linking that the 74 `configure' script does not know about. Run `./configure --help' for 75 details on some of the pertinent environment variables. 73 76 74 77 You can give `configure' initial values for configuration parameters … … 83 86 ==================================== 84 87 85 You can compile the package for more than one kind of computer at the88 You can compile the package for more than one kind of computer at the 86 89 same time, by placing the object files for each architecture in their 87 90 own directory. To do this, you must use a version of `make' that … … 100 103 ================== 101 104 102 By default, `make install' will install the package's files in105 By default, `make install' will install the package's files in 103 106 `/usr/local/bin', `/usr/local/man', etc. You can specify an 104 107 installation prefix other than `/usr/local' by giving `configure' the 105 option `--prefix=P ATH'.108 option `--prefix=PREFIX'. 106 109 107 110 You can specify separate installation prefixes for 108 111 architecture-specific files and architecture-independent files. If you 109 give `configure' the option `--exec-prefix=P ATH', the package will use110 PATHas the prefix for installing programs and libraries.112 give `configure' the option `--exec-prefix=PREFIX', the package will 113 use PREFIX as the prefix for installing programs and libraries. 111 114 Documentation and other data files will still use the regular prefix. 112 115 113 116 In addition, if you use an unusual directory layout you can give 114 options like `--bindir= PATH' to specify different values for particular117 options like `--bindir=DIR' to specify different values for particular 115 118 kinds of files. Run `configure --help' for a list of the directories 116 119 you can set and what kinds of files go in them. … … 123 126 ================= 124 127 125 Some packages pay attention to `--enable-FEATURE' options to128 Some packages pay attention to `--enable-FEATURE' options to 126 129 `configure', where FEATURE indicates an optional part of the package. 127 130 They may also pay attention to `--with-PACKAGE' options, where PACKAGE … … 138 141 ========================== 139 142 140 There may be some features `configure' cannot figure out 141 automatically, but needs to determine by the type of machine the package 142 will run on. Usually, assuming the package is built to be run on the 143 _same_ architectures, `configure' can figure that out, but if it prints 144 amessage saying it cannot guess the machine type, give it the143 There may be some features `configure' cannot figure out automatically, 144 but needs to determine by the type of machine the package will run on. 145 Usually, assuming the package is built to be run on the _same_ 146 architectures, `configure' can figure that out, but if it prints a 147 message saying it cannot guess the machine type, give it the 145 148 `--build=TYPE' option. TYPE can either be a short name for the system 146 149 type, such as `sun4', or a canonical name which has the form: … … 168 171 ================ 169 172 170 If you want to set default values for `configure' scripts to share, 171 you can create a site shell script called `config.site' that gives 172 defaultvalues for variables like `CC', `cache_file', and `prefix'.173 If you want to set default values for `configure' scripts to share, you 174 can create a site shell script called `config.site' that gives default 175 values for variables like `CC', `cache_file', and `prefix'. 173 176 `configure' looks for `PREFIX/share/config.site' if it exists, then 174 177 `PREFIX/etc/config.site' if it exists. Or, you can set the … … 179 182 ================== 180 183 181 Variables not defined in a site shell script can be set in the184 Variables not defined in a site shell script can be set in the 182 185 environment passed to `configure'. However, some packages may run 183 186 configure again during the build, and the customized values of these … … 193 196 ====================== 194 197 195 `configure' recognizes the following options to control how it 196 operates. 198 `configure' recognizes the following options to control how it operates. 197 199 198 200 `--help'
Note:
See TracChangeset
for help on using the changeset viewer.

