VirtualBox

Changeset 280 in kBuild for branches/GNU/src/gmake/INSTALL


Ignore:
Timestamp:
May 16, 2005 4:54:02 PM (19 years ago)
Author:
bird
Message:

Current make snaphot, 2005-05-16.

Location:
branches/GNU/src/gmake
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/GNU/src/gmake

    • Property svn:ignore
      •  

        old new  
        3434README.DOS
        3535README.W32
         36README.OS2
        3637aclocal.m4
        3738autom4te.cache
  • 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
     1Installation Instructions
     2*************************
     3
     4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
     5Software Foundation, Inc.
     6
     7This file is free documentation; the Free Software Foundation gives
    58unlimited permission to copy, distribute and modify it.
    69
     
    811==================
    912
    10    These are generic installation instructions.
     13These are generic installation instructions.
    1114
    1215   The `configure' shell script attempts to guess correct values for
     
    6871=====================
    6972
    70    Some systems require unusual options for compilation or linking that
    71 the `configure' script does not know about.  Run `./configure --help'
    72 for details on some of the pertinent environment variables.
     73Some systems require unusual options for compilation or linking that the
     74`configure' script does not know about.  Run `./configure --help' for
     75details on some of the pertinent environment variables.
    7376
    7477   You can give `configure' initial values for configuration parameters
     
    8386====================================
    8487
    85    You can compile the package for more than one kind of computer at the
     88You can compile the package for more than one kind of computer at the
    8689same time, by placing the object files for each architecture in their
    8790own directory.  To do this, you must use a version of `make' that
     
    100103==================
    101104
    102    By default, `make install' will install the package's files in
     105By default, `make install' will install the package's files in
    103106`/usr/local/bin', `/usr/local/man', etc.  You can specify an
    104107installation prefix other than `/usr/local' by giving `configure' the
    105 option `--prefix=PATH'.
     108option `--prefix=PREFIX'.
    106109
    107110   You can specify separate installation prefixes for
    108111architecture-specific files and architecture-independent files.  If you
    109 give `configure' the option `--exec-prefix=PATH', the package will use
    110 PATH as the prefix for installing programs and libraries.
     112give `configure' the option `--exec-prefix=PREFIX', the package will
     113use PREFIX as the prefix for installing programs and libraries.
    111114Documentation and other data files will still use the regular prefix.
    112115
    113116   In addition, if you use an unusual directory layout you can give
    114 options like `--bindir=PATH' to specify different values for particular
     117options like `--bindir=DIR' to specify different values for particular
    115118kinds of files.  Run `configure --help' for a list of the directories
    116119you can set and what kinds of files go in them.
     
    123126=================
    124127
    125    Some packages pay attention to `--enable-FEATURE' options to
     128Some packages pay attention to `--enable-FEATURE' options to
    126129`configure', where FEATURE indicates an optional part of the package.
    127130They may also pay attention to `--with-PACKAGE' options, where PACKAGE
     
    138141==========================
    139142
    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 a message saying it cannot guess the machine type, give it the
     143There may be some features `configure' cannot figure out automatically,
     144but needs to determine by the type of machine the package will run on.
     145Usually, assuming the package is built to be run on the _same_
     146architectures, `configure' can figure that out, but if it prints a
     147message saying it cannot guess the machine type, give it the
    145148`--build=TYPE' option.  TYPE can either be a short name for the system
    146149type, such as `sun4', or a canonical name which has the form:
     
    168171================
    169172
    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 default values for variables like `CC', `cache_file', and `prefix'.
     173If you want to set default values for `configure' scripts to share, you
     174can create a site shell script called `config.site' that gives default
     175values for variables like `CC', `cache_file', and `prefix'.
    173176`configure' looks for `PREFIX/share/config.site' if it exists, then
    174177`PREFIX/etc/config.site' if it exists.  Or, you can set the
     
    179182==================
    180183
    181    Variables not defined in a site shell script can be set in the
     184Variables not defined in a site shell script can be set in the
    182185environment passed to `configure'.  However, some packages may run
    183186configure again during the build, and the customized values of these
     
    193196======================
    194197
    195    `configure' recognizes the following options to control how it
    196 operates.
     198`configure' recognizes the following options to control how it operates.
    197199
    198200`--help'
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette