Received: (qmail 10049 invoked by uid 2012); 10 Mar 1999 21:28:49 -0000 Message-Id: <19990310212849.10048.qmail@hyperreal.org> Date: 10 Mar 1999 21:28:49 -0000 From: Peter Santo Reply-To: peter@pool.informatik.rwth-aachen.de To: apbugs@hyperreal.org Subject: Cannot make suexec under Solaris 2.6 X-Send-Pr-Version: 3.2 >Number: 4030 >Category: suexec >Synopsis: Cannot make suexec under Solaris 2.6 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Mar 10 13:30:01 PST 1999 >Closed-Date: Thu Apr 13 12:24:38 PDT 2000 >Last-Modified: Thu Apr 13 12:24:38 PDT 2000 >Originator: peter@pool.informatik.rwth-aachen.de >Release: 1.3.4 >Organization: >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. >Release-Note: >Audit-Trail: From: Peter Franken To: apbugs@hyperreal.org, apache-bugdb@apache.org Cc: Subject: Re: suexec/4030: Cannot make suexec under Solaris 2.6 Date: Thu, 11 Mar 1999 00:42:13 +0100 Hi, apbugs@hyperreal.org schrieb: > Thank you very much for your problem report. > It has the internal identification `suexec/4030'. > The individual assigned to look at your > report is: apache. > > >Category: suexec > >Responsible: apache > >Synopsis: Cannot make suexec under Solaris 2.6 > >Arrival-Date: Wed Mar 10 13:30:01 PST 1999 Since I'm not running Solaris on any of the systems I have access to, I guess, I'm not the one who'd sent a problem report. This assumption is not proven but at least hardened by the fact, that I can't remember neither the situation prior to the fault no r the fault itself. In this case, you should try to reach the other guy who'd made this experience in his personal reality. In any other case, try "42" as the most probable answer to any of your upcoming questions belonging to this concern. This is just a proposal, but better than just hot air, which is the stuff all other answers you could request from me would consist of - as far as they belong to the category mentioned above. Ok, guys, it's about 0:45h AM and, re-reading my reply to your mail, it's definitely time to go to bed. Have a nice day :-) A bientôt Peter State-Changed-From-To: open-feedback State-Changed-By: coar State-Changed-When: Fri Jan 7 14:28:26 PST 2000 State-Changed-Why: Please re-try your build with Apache 1.3.9 and the APACI method (apache-1.3/configure, make, make install) and see if the problem still exists. From: Chris Bongaarts To: apbugs@apache.org Cc: Subject: Re: suexec/4030: Cannot make suexec under Solaris 2.6 Date: Fri, 3 Mar 2000 11:17:25 -0600 (CST) FYI: This bug (suexec/4030) was reintroduced in or before Apache 1.3.12 due to the addition of the $(suexec_umask) parameter to the EXTRA_CFLAGS. Here is a patch (to the generated Makefile, but looks like it would apply fine to Makefile.tmpl) that makes it work on my configuration. ---begin patch--- *** Makefile.orig Thu Mar 2 18:13:55 2000 --- Makefile Fri Mar 3 11:09:03 2000 *************** *** 207,212 **** --- 207,213 ---- if [ ".$(suexec)" = .1 ]; then \ $(MAKE) $(MFLAGS) \ EXTRA_CFLAGS='\ + $(suexec_umask) \ -DHTTPD_USER=\"$(suexec_caller)\" \ -DUID_MIN=$(suexec_uidmin) \ -DGID_MIN=$(suexec_gidmin) \ *************** *** 213,220 **** -DUSERDIR_SUFFIX=\"$(suexec_userdir)\" \ -DLOG_EXEC=\"$(suexec_logexec)\" \ -DDOC_ROOT=\"$(suexec_docroot)\" \ ! -DSAFE_PATH=\"$(suexec_safepath)\" \ ! $(suexec_umask)' \ suexec; \ fi @echo "<=== $(SRC)/support" --- 214,220 ---- -DUSERDIR_SUFFIX=\"$(suexec_userdir)\" \ -DLOG_EXEC=\"$(suexec_logexec)\" \ -DDOC_ROOT=\"$(suexec_docroot)\" \ ! -DSAFE_PATH=\"$(suexec_safepath)\"' \ suexec; \ fi @echo "<=== $(SRC)/support" ---end patch--- %% Christopher A. Bongaarts %% cab@tc.umn.edu %% %% Internet Services %% http://umn.edu/~cab %% %% University of Minnesota %% +1 (612) 625-1809 %% State-Changed-From-To: feedback-closed State-Changed-By: coar State-Changed-When: Thu Apr 13 12:24:37 PDT 2000 State-Changed-Why: Fixed in the next release after 1.3.12. Thanks! >Unformatted: >Quarter: >Keywords: >Date-Required: [In order for any reply to be added to the PR database, ] [you need to include 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! ]