cvs commit: apache-1.3/src PORTING

[ji...@hyperreal.org]

jim         98/07/13 05:31:05

  Modified:    src      PORTING
  Log:
  Some doc changes about the header rename
  
  Revision  Changes    Path
  1.31      +17 -11    apache-1.3/src/PORTING
  
  Index: PORTING
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/src/PORTING,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- PORTING	1998/06/04 20:18:27	1.30
  +++ PORTING	1998/07/13 12:31:04	1.31
  @@ -97,7 +97,7 @@
   for the port:
   
      ./Configure
  -   ./include/conf.h
  +   ./include/ap_config.h
   
   Configure:
   ==========
  @@ -117,7 +117,7 @@
   
   The 'OS' variable is used to define the system Apache is being built
   for. You will also note that 'CFLAGS' defines "-DAUX". In this case,
  -'AUX' is a magic cookie used by the Apache code (mainly conf.h [see
  +'AUX' is a magic cookie used by the Apache code (mainly ap_config.h [see
   below]) to handle OS-specific code. Each code that has and requires
   such OS-specific code will require a unique "system cookie" defined
   in 'CFLAGS'. You will also note that Configure also goes ahead and
  @@ -129,9 +129,9 @@
   than any system supplied regex.  It's been our experience that system
   supplied regex libraries are generally buggy, and should be avoided.
   
  -conf.h:
  +ap_config.h:
   =======
  -The Apache code, specifically in conf.h, uses a variety of #defines to
  +The Apache code, specifically in ap_config.h, uses a variety of #defines to
   control how the code is compiled and what options are available for each
   supported OS. One of the hardest parts about the porting process is
   determining which of the following are applicable for your system and
  @@ -152,7 +152,7 @@
   are not strictly required, but are a Good Idea anyway).
   
   The following several lines provide a list and short description
  -of these #defines. By correctly #defining the ones you need in conf.h
  +of these #defines. By correctly #defining the ones you need in ap_config.h
   (wrapped by the above mentioned "system cookie"), you can fine tune the
   build for your OS.
   
  @@ -187,15 +187,21 @@
         Define if the OS supports the getrlimit()/setrlimit() functions
   
       HAVE_CRYPT_H:
  -      Define if the OS has the <crypt.h> header file.
  +      Defined if the OS has the <crypt.h> header file. This is set
  +      automatically during the Configure process and stored in the
  +      src/include/ap_config_auto.h header file.
   
       HAVE_SYS_SELECT_H:
  -      Define if the OS has the <sys/select.h> header file.
  +      Defined if the OS has the <sys/select.h> header file. This is
  +      set automatically during the Configure process and stored in the
  +      src/include/ap_config_auto.h header file.
   
       HAVE_SYS_RESOURCE_H:
  -      Define if the OS has and supports the getrlimit/setrlimit
  +      Defined if the OS has and supports the getrlimit/setrlimit
         family. Apache uses this to determine if RLIMIT_CPU|VMEM|DATA|RLIMIT
  -      is found and used.
  +      is found and used. This is set automatically during the Configure
  +      process and stored in the src/include/ap_config_auto.h header
  +      file.
   --
   
    USE_*:
  @@ -338,8 +344,8 @@
         NET_SIZE_T:
          Some functions such as accept(), getsockname(), getpeername() take
          an int *len on some architectures and a size_t *len on others.
  -       If left undefined apache will default it to int.  See include/conf.h
  -       for a description of NET_SIZE_T.
  +       If left undefined apache will default it to int.  See
  +       include/ap_config.h for a description of NET_SIZE_T.
   
         NEED_HASHBANG_EMUL:
          The execve()/etc. functions on this platform do not deal with #!,