Received: (qmail 24469 invoked by uid 2012); 30 Apr 1999 06:19:53 -0000
Message-Id: <19990430061953.24468.qmail@hyperreal.org>
Date: 30 Apr 1999 06:19:53 -0000
From: Dave Williams <d.williams@murdoch.edu.au>
Reply-To: d.williams@murdoch.edu.au
To: apbugs@hyperreal.org
Subject: make fails with suEXEC support
X-Send-Pr-Version: 3.2

>Number:         4337
>Category:       suexec
>Synopsis:       make fails with suEXEC support
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          duplicate
>Submitter-Id:   apache
>Arrival-Date:   Thu Apr 29 23:20:04 PDT 1999
>Closed-Date:    Fri Jan 07 14:29:47 PST 2000
>Last-Modified:  Fri Jan 07 14:29:47 PST 2000
>Originator:     d.williams@murdoch.edu.au
>Release:        1.3.6
>Organization:
>Environment:
SunOS tigre 5.7 Generic sun4u sparc SUNW,Ultra-250 
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.8.1/specs
gcc version 2.8.1
>Description:
While compiling apache 1.3.6 on solaris 2.7 and adding suEXEC support I
get the following fatal error with the extra line continuation after
-DSAFE_PATH=....  

Our central IT area suggest its in one of the make files, any ideas.

gcc  -DSOLARIS2=270 `../apaci` ab.o -o ab   -L../os/unix -L../ap -los
-lap  -lso
cket -lnsl
gcc -c  -I../os/unix -I../include   -DSOLARIS2=270 \
                -DHTTPD_USER=\"httpd\" \
                -DUID_MIN=1000 \
                -DGID_MIN=10 \
                -DUSERDIR_SUFFIX=\"public\" \
                -DLOG_EXEC=\"/usr/local/apache/logs/suexec_log\" \
                -DDOC_ROOT=\"/usr/local/apache/htdocs\" \
                -DSAFE_PATH=\"/usr/local/bin:/usr/bin:/bin\" \ suexec.c
                                                      =======^
gcc:  suexec.c: No such file or directory
gcc: No input files
*** Error code 1
make: Fatal error: Command failed for target `suexec.o'
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: coar
State-Changed-When: Fri Jan  7 14:29:46 PST 2000
State-Changed-Why:
[This is a standard response.]
This issue has been reported before;
please search the FAQ and the bug database.
Thanks for using Apache!
Class-Changed-From-To: sw-bug-duplicate
Class-Changed-By: coar
Class-Changed-When: Fri Jan  7 14:29:46 PST 2000
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]