The following reply was made to PR other/4343; it has been noted by GNATS.
From: "Ralf S. Engelschall" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Subject: Re: other/4343: Activating a new module as a DSO
Date: Mon, 17 May 1999 10:11:32 +0200
In article <[EMAIL PROTECTED]> you wrote:
>>Synopsis: Activating a new module as a DSO
> [...]
> The configure script doesn't seem to support activating
> a new module as a DSO.
No, it _does_ support this.
> 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
I've tried this with a sample module and it worked fine. I don't know why
--enable-shared=blah doesn't work for you, but the code is correct and it
works for me. I cannot reproduce your problem.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
