build/6839: Makefile.tmpl sets wrong include path

[Matthias Rahlf <ra...@fs.tum.de>]

>Number:         6839
>Category:       build
>Synopsis:       Makefile.tmpl sets wrong include path
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Nov 13 17:20:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     rahlf@fs.tum.de
>Release:        1.3.14
>Organization:
apache
>Environment:
Linux webding 2.0.36 #2 Sun Feb 21 15:55:27 EST 1999 i586 unknown
Debian potato
>Description:
apache 1.3.11 is installed under /usr/local/stow/apache-1.3.11
and linked from /usr/local/bin, /usr/local/include, /usr/local/libexec, ...
I am now compiling apache-1.3.14:
...
gcc -c -I/usr/local/include -I../os/unix -I../include   -DLINUX=2 -DMOD_SSL=207101 -DUSE_HSREGEX -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -fpic -DSHARED_CORE -O2 -I/usr/local/include/ -L/usr/X11R6/lib -I/usr/X11R6/include `../apaci` http_core.c
The headerfiles from /usr/local/include are now taken instead of the ones from ../include
Therefore ADD_DEFAULT_CHARSET_UNSET is undefined and the build process aborts.
>How-To-Repeat:

>Fix:
change 
INCLUDES=$(INCLUDES1) $(INCLUDES0)
to
INCLUDES=$(INCLUDES0) $(INCLUDES1)
>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!     ]