Changeset 338

Show
Ignore:
Timestamp:
07/06/07 23:27:52 (1 year ago)
Author:
florida
Message:

version initiale wifidog-1.1.3-rc1

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • wifidog/wifidog-client/INSTALL

    r218 r338  
    22************************* 
    33 
    4 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free 
    5 Software Foundation, Inc. 
     4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 
     52006 Free Software Foundation, Inc. 
    66 
    77This file is free documentation; the Free Software Foundation gives 
    …… 
    1111================== 
    1212 
    13 These are generic installation instructions. 
     13Briefly, the shell commands `./configure; make; make install' should 
     14configure, build, and install this package.  The following 
     15more-detailed instructions are generic; see the `README' file for 
     16instructions specific to this package. 
    1417 
    1518   The `configure' shell script attempts to guess correct values for 
    …… 
    2427   It can also use an optional file (typically called `config.cache' 
    2528and enabled with `--cache-file=config.cache' or simply `-C') that saves 
    26 the results of its tests to speed up reconfiguring.  (Caching is 
     29the results of its tests to speed up reconfiguring.  Caching is 
    2730disabled by default to prevent problems with accidental use of stale 
    28 cache files.) 
     31cache files. 
    2932 
    3033   If you need to do unusual things to compile the package, please try 
    …… 
    3639 
    3740   The file `configure.ac' (or `configure.in') is used to create 
    38 `configure' by a program called `autoconf'.  You only need 
    39 `configure.ac' if you want to change it or regenerate `configure' using 
    40 a newer version of `autoconf'. 
     41`configure' by a program called `autoconf'.  You need `configure.ac' if 
     42you want to change it or regenerate `configure' using a newer version 
     43of `autoconf'. 
    4144 
    4245The simplest way to compile this package is: 
    4346 
    4447  1. `cd' to the directory containing the package's source code and type 
    45      `./configure' to configure the package for your system.  If you're 
    46      using `csh' on an old version of System V, you might need to type 
    47      `sh ./configure' instead to prevent `csh' from trying to execute 
    48      `configure' itself. 
    49  
    50      Running `configure' takes awhile.  While running, it prints some 
    51      messages telling which features it is checking for. 
     48     `./configure' to configure the package for your system. 
     49 
     50     Running `configure' might take a while.  While running, it prints 
     51     some messages telling which features it is checking for. 
    5252 
    5353  2. Type `make' to compile the package. 
    …… 
    7979is an example: 
    8080 
    81      ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix 
     81     ./configure CC=c99 CFLAGS=-g LIBS=-lposix 
    8282 
    8383   *Note Defining Variables::, for more details. 
    …… 
    8888You can compile the package for more than one kind of computer at the 
    8989same time, by placing the object files for each architecture in their 
    90 own directory.  To do this, you must use a version of `make' that 
    91 supports the `VPATH' variable, such as GNU `make'.  `cd' to the 
     90own directory.  To do this, you can use GNU `make'.  `cd' to the 
    9291directory where you want the object files and executables to go and run 
    9392the `configure' script.  `configure' automatically checks for the 
    9493source code in the directory that `configure' is in and in `..'. 
    9594 
    96    If you have to use a `make' that does not support the `VPATH' 
    97 variable, you have to compile the package for one architecture at a 
    98 time in the source code directory.  After you have installed the 
    99 package for one architecture, use `make distclean' before reconfiguring 
    100 for another architecture. 
     95   With a non-GNU `make', it is safer to compile the package for one 
     96architecture at a time in the source code directory.  After you have 
     97installed the package for one architecture, use `make distclean' before 
     98reconfiguring for another architecture. 
    10199 
    102100Installation Names 
    …… 
    191189 
    192190causes the specified `gcc' to be used as the C compiler (unless it is 
    193 overridden in the site shell script).  Here is a another example: 
    194  
    195      /bin/bash ./configure CONFIG_SHELL=/bin/bash 
    196  
    197 Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent 
    198 configuration-related scripts to be executed by `/bin/bash'. 
     191overridden in the site shell script). 
     192 
     193Unfortunately, this technique does not work for `CONFIG_SHELL' due to 
     194an Autoconf bug.  Until the bug is fixed you can use this workaround: 
     195 
     196     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash 
    199197 
    200198`configure' Invocation