>Number: 3718 >Category: config >Synopsis: make says Apache not configured for DSO support >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: open >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Tue Jan 19 14:10:00 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.4 >Environment: RedHat Linux 5.1, Apache 1.3.4, JServ 1.0b2 Apache 1.3.4 installed with DSO Non jserv modules show up in /libexec. >Description: Apache install = /usr/local/apache Apache src = /usr/local/src/apache/apache_1.3.4 Jserv src = /usr/local/src/jserv/Apache-JServ_1.0b2
from Jserv src dir: ./configure --with-apache-install=/usr/local/apache make reports that apache is not configured for DSO support but non-jserv modules do appear in /libexec. I tried ./configure without parameters then used make. It found the apache install and proceeded without error msgs. The Java classes were compiled but mod_jserv.c was not. >How-To-Repeat: Try putting the apache-installation, the apache-src and jserv-src in different directories. It looks to me like some install script or make file is making assumptions about the paths and ignoring the param --with-apache-install supplied to configure. >Fix: I had a friend help me. This is our workaround. First we compiled Apache with DSO support. We created a a configuration using ./configure and make file for DSO, and vefied that it worked by checking /libexec in the apache install dir. Then we re-compiled JServ statically into Apache. >From jserv dir: ./configure --with-apache-src=/usr/local/src/jserv/Apache-JServ_1.0b2 \ --enable-apache-config (I think this was the cmd) make This seemed to add the proper info to the makefile in the apache src dir without changing our previous DSO instructions. Then cd to apache src dir: Without calling ./configure again... make make install This recompiled Apache and statically linked mod_jserv while keeping our other modules linked dynamically. >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! ]
