>Number: 4343 >Category: other >Synopsis: Activating a new module as a DSO >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Sat May 1 08:30:00 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: Solaris 2.5 -- Generic_103093-25 sun4u sparc SUNW,Ultra-1 >Description: The configure script doesn't seem to support activating a new module as a DSO. I tried various combinations of the --activate-module and --enable-shared options to no avail. >How-To-Repeat: My scenario consisted of creating a src/modules/blah directory with the right stuff to build libblah.so and then running configure as follows:
./configure --shadow --enable-module=so --enable-module=most \ --enable-shared=proxy --activate-module=src/modules/blah/libblah.so \ --enable-shared=blah >Fix: I got around it by adding an --activate-shared option. My bloated implementation duplicates the --activate-module code, with a few small changes, and works for me on Solaris like this: ./configure --shadow --enable-module=so --enable-module=most \ --enable-shared=proxy --activate-shared=src/modules/blah/libblah.so The only changes over --with-activate-module are: > echo "## (configure --activate-shared=$file)" >>$addconf > echo "SharedModule $modfile" >>$addconf and: > eval "shared_$module=yes" >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! ]
