>Number: 4030
>Category: suexec
>Synopsis: Cannot make suexec under Solaris 2.6
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Wed Mar 10 13:30:01 PST 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.4
>Environment:
Sun Ultra-1, Solaris 2.6 (aka SunOS 5.6) and its make, gcc 2.8.1
>Description:
After configuring apache 1.3.4 for suexec, make stops when trying to build
suexec.o from suexec.c. This is due to a simple typo in the top-level Makefile.
The source code cannot be found and make exits with something like:
--------------------- screen output BEGIN --------------------------
gcc -c -I../os/unix -I../include -DSOLARIS2=260 \
-DHTTPD_USER=\"www\" \
-DUID_MIN=100 \
-DGID_MIN=100 \
-DUSERDIR_SUFFIX=\"public_html\" \
-DLOG_EXEC=\"/usr/local/apache/logs/suexec_log\" \
-DDOC_ROOT=\"/usr/local/apache/htdocs\" \
-DSAFE_PATH=\"/usr/local/bin:/usr/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'
Current working directory /tmp/apache_1.3.4/src/support
*** Error code 1
make: Fatal error: Command failed for target `build-support'
Current working directory /tmp/apache_1.3.4
*** Error code 1
make: Fatal error: Command failed for target `build'
--------------------- screen output END --------------------------
The problem is the line
-DSAFE_PATH=\"/usr/local/bin:/usr/bin\" \ suexec.c
^^^
>How-To-Repeat:
I think, anyone who tries to build apache 1.3.4 with suexec gets this error.
I did exactly what is described in the README.configure example (line 98ff).
>Fix:
I fixed the problem by editing the Makefile manually. Here the patch
-------- patch BEGIN --------------------
181c181,182
< -DSAFE_PATH=\"$(suexec_safepath)\"' \
---
> -DSAFE_PATH=\"$(suexec_safepath)\" \
> ' \
-------- patch BEGIN --------------------
A better way would be to correct the mistake in the templates/configure script,
but I lack the knowledge and time to do so.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> 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! ]
