build/6907: build time CFLAGS not passed to "suexec" Makefile

[Daniel Thibadeau <da...@hp.com>]

>Number:         6907
>Category:       build
>Synopsis:       build time CFLAGS not passed to "suexec" Makefile
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Nov 28 10:50:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     dan_thibadeau@hp.com
>Release:        1.3.14
>Organization:
apache
>Environment:
uname -a ="HP-UX boi316 B.11.00 A 9000/800 683319373 two-user license"
Compiler ="B3901BA B.11.01.20 HP C/ANSI C Developer's Bundle for HP-UX 11.00 (S800)"
>Description:
./Makefile sets EXTRA_CFLAGS on the command line when it runs "make" to build
the "suexec" binary file.  The command line has precidence over the EXTRA_CFLAGS
value defined in the ./src/support/Makefile.  Therefore any values of CFLAGS
set when ./configure is run will be ignored when building "suexec".
>How-To-Repeat:
export CFLAGS="+DAportable"
./configure --enable-suexec --suexec-caller=www

If you run the above, you will see that "+DAportable" is passed to all "cc"
commands EXCEPT the one that builds "suexec".
>Fix:
In ./Makefile.tmpl instead of passing "EXTRA_CFLAGS" on the command line use
"EXTRA_SU_CFLAGS" (line 197), and in ./src/support/Makefile.tmpl add
"$(EXTRA_SU_CFLAGS)" to the end of the "CFLAGS=" definition (line 2).
>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!     ]