On Tue, Mar 29, 2016 at 8:52 PM, Yann Ylavic <ylavic.dev@xxxxxxxxx> wrote:
> On Tue, Mar 29, 2016 at 7:52 PM, Leonay Wynn <lwkj328@xxxxxxxxx> wrote:
>> I need to upgrade from 2.2 to to 2.4
>>
>> i used ./configure --prefix=/apps/httpd --enable-ssl
>> --with-ssl=/usr/local/ssl --with-mpm=worker --enable-module=headers
>>
>> as well as
>> ./configure --prefix=/apps/httpd --enable-so --enable-ssl
>> --with-ssl=/usr/local/ssl --with-mpm=worker --enable-module=headers
>
> Doesn't this create (at least) the mod_ssl.so file in
> /apps/httpd/modules/ directory?
>
> For mod_headers.so, as I said in the other thread, the correct way to
> enable the build of a module is --enable-<module_name> (for
> mod_<module_name>.so), thus for mod_header: --enable-headers.
>
> I think shared modules (i.e. .so files) are used by default with this
> method, but otherwise you could specify it explicitely:
> --enable-ssl=shared --enable-headers=shared.
>
> So the complete command should be something like:
> $ ./configure --prefix=/apps/httpd --enable-so --enable-ssl=shared
> --enable-headers=shared --with-ssl=/usr/local/ssl --with-mpm=worker
>
> Also, please note the modules are really installed once you do the
> usual "make && sudo make install" after the above "./configure".
Hmm, actually you may need to do a "make depend" first (ie. make
depend && make && sudo make install) for all the ./configured modules
to be taken into account.
>
> Regards,
> Yann.
|