You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Tim Mooney <mo...@dogbert.cc.ndsu.nodak.edu> on 2001/03/12 20:18:07 UTC

build/7393: The ap_config_auto.h is missing the last #endif at the end of the file.

>Number:         7393
>Category:       build
>Synopsis:       The ap_config_auto.h is missing the last #endif at the end of the file.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Mar 12 11:20:04 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     mooney@dogbert.cc.ndsu.nodak.edu
>Release:        1.3.19
>Organization:
apache
>Environment:
all / all
>Description:
While trying to compile apache 1.3.19 + php 3.0.18 on IRIX 6.5.11m, the
compilation stopped, because of a missing #endif:

 
cc-1037 cc: ERROR File = ../apache_1.3.19/src/include/ap_config_auto.h, Line = 6
  A "#endif" directive is missing from the source file.

  #ifndef AP_CONFIG_AUTO_H
   ^

cc-1037 cc: ERROR File = ../apache_1.3.19/src/include/ap_config_auto.h, Line = 6
  A "#endif" directive is missing from the source file.

  #ifndef AP_CONFIG_AUTO_H
   ^


Sure enough, the #endif that should close the header guard #ifdef is missing.
Grep'ing the source, it would seem that src/Configure is missing the necessary
line to echo that last #endif into the generated ap_config_auto.h
>How-To-Repeat:
Try compile something that uses 1.3.19's ap_config_auto.h with a really
picky compiler.
>Fix:
--- apache_1.3.19/src/Configure.orig    Mon Feb 19 07:32:54 2001
+++ apache_1.3.19/src/Configure Mon Mar 12 12:43:57 2001
@@ -991,6 +991,7 @@
     fi
 done
 )
+echo "#endif /* AP_CONFIG_AUTO_H */" >>$AP_CONFIG_AUTO_H
 
 ####################################################################
 # Special AIX 4.x support: need to check for sys/processor.h
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]