On Thu, Nov 19, 1998, Anthony Rumble wrote:
> [...]
> > Makes no difference? You mean when libssl.so is not loaded httpd still
> > segfaults? Then the problem cannot be directly inside mod_ssl. Then it's
> > perhaps related to the Extended API or even to a problem between mod_perl and
> > the EAPI? Make sure mod_perl is compiled with -DEAPI, too! Else you get
> > segfaults, of course.
>
> Upgraded to mod_perl 1.16 for starters.
>
> Now, the RPM for mod_perl is using DSO and APXS, and of course the
> origional redhat build of apache doesn't have -DEAPI..
>
> Anyway.. once I put in my apache-mod_ssl-1.3.3-2.1.0 rpm modules in,
> including the devel module, and then re-built the mod_perl module.. -DEAPI
> was there.. and it all seems to work now.
Fine. Then your problem was not a bug in mod_ssl or mod_perl.
It was just because you didn't followed the mod_ssl INSTALL file ;-)
> Maby we need to get redhat to put in -DEAPI in by default, then maby we
> can can put up third party mod_ssl RPM's up say on ftp.replay.com
No, just -DEAPI is useless. One needs also the EAPI patch itself. The only
thing they can do is to compile their Apache with EAPI (but not mod_ssl)
applied. There is a --with-eapi-only option in mod_ssl's configure for this
purpose.
> Then anyone can have a working SSL apache without having to compile or
> patch anything, and still take advantage of redhats bug fixes/updates..
> etc
Hmmmm... my personal opinion is not to use RH's Apache RPM's etc. When I
would run RH I would use only an own compiled Apache+mod_ssl+mod_perl+whatever
bundle and not intermix RH's SRPM stuff with third party stuff.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
