trawick at gmail
Oct 18, 2009, 7:35 AM
Post #4 of 4
(359 views)
Permalink
|
On Wed, May 27, 2009 at 7:13 PM, William A. Rowe, Jr.
<wrowe [at] rowe-clan> wrote:
> Jeff Trawick wrote:
>> On Wed, May 27, 2009 at 4:26 PM, William A. Rowe, Jr.
>> <wrowe [at] rowe-clan <mailto:wrowe [at] rowe-clan>> wrote:
>>
>> and --enable-mods-shared=all still results in (unlinked) static
>> libevent.a, libworker.a objects, instead of .so's. Any clues?
>>
>>
>> 1. the idea discussed (or not complained about) previously is to provide
>> something like --with-mpm-shared={list|all}*
>> 2. I haven't finished implementing it yet
>>
>> so if you specify "--with-mpm=shared" you'll still have to apxs in your MPM
>>
>> *unlike --enable-mods-shared, if more than one is selected then the
>> LoadModule end of this would be smart enough to avoid loading more than
>> one by default, and hopefully let you -Define a symbol to select a
>> non-default one (e.g., -DEVENT)
>
> should we tweak the 'help' to not show --with-mpm=shared?
I'll do that in the very short term.
> FWIW; enable-mpms=shared would be the proper feature-toggle, while the
> --with-mpm=choice should specify the one loaded by default. At least by
> autoconf convention.
Makes sense.
(Staring at config has re-commenced.)
|
