2-Jan-99 16:59 you wrote:
> On Sat, Jan 02, 1999, Achille M. Luongo wrote:
>> I would like to compile or simply use a mod_ssl module under Linux
>> (kernel 2.0.36) as a stand-alone DSO module for an apache 1.3.3 binary
>>
>> RPM package, but I didn't find istructions.
>> Can anyone suggest me how to build mod_ssl as a stand-alone DSO module ?
>> Is already available a RPM module with a DSO version of mod_ssl for such
>> a kernel ?
> How about this part of the INSTALL file in the mod_ssl distribution?
> | Upgrading with APXS (EXPERTS ONLY)
> | __________________________________
> |
> | Once you've built and installed Apache with mod_ssl as a DSO (libssl.so) you
> | can easily upgrade this libssl.so file with a stand-alone built procedure as
> | long as the Extended API (EAPI) didn't change and you've SSLeay installed
> | somewhere. For this you can use the following procedure:
> |
> | $ cd mod_ssl-2.1.x-1.3.x ALL
> | $ ./configure \ ALL
> | --with-apxs[=/path/to/apache/sbin/apxs] \ ALL
> | --with-ssleay=/path/to/ssleay \ ALL
> | --with-rsaref=/path/to/rsaref US
> | $ make ALL
> | $ make install ALL
> | $ make distclean ALL
> |
> | This will build mod_ssl locally inside the pkg.modssl/ directory and then
> | upgrades your existing libssl.so file. This approach is also interesting for
> | package vendors. Because those can create an Apache+EAPI package (with the
> | use of --with-eapi-only) and a APXS-based mod_ssl package (with the use of
> | --with-apxs).
> But please read it carefully: The generated libssl.so doesn't work with a
> plain Apache. Your Apache has to already contain the Extended API.
Thnx god this is minor problem: without patched Apache libssl.so will not be
created in first place -- compilation will fail :-)
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
