On Thu, 3 Dec 1998, Ralf S. Engelschall wrote:
: Just a question? Why do you have to load libcrypto.so and libssl.so manually?
: Because of a.out?
Yes. Some NetBSD ports are a.out (including the very popular i386 and
sparc), others are ELF. To reduce confusion and keep it more cross-platform
friendly, the build process I used doesn't assume that ELFisms are
available.
: one more question: What's the reason you have to name the DSO mod_ssl.so
: instead of libssl.so? Because of the conflict with the "real" libssl.so?
Conformity with "the rest of the world;" other apxs compiled modules,
including those available through the NetBSD pkgsrc system, typically end up
mod_modulename.so. The program is even called mod_ssl... ;)
: Ops, seems like I was too slow or you too fast. Last weekend I've added full
: APXS support to the distribution. I think this would make your life easier.
: When you're interesting you can test my APXS support. I've still not comitted
: it for mod_ssl 2.1.x because it's not enough tested. But it already works
: fine for me. You just have to use --with-apxs instead of --with-apache and
: anything else works magically ;-) Let it me know when I can use you as a
: beta-tester for this stuff...
I'll look at it. What I did notice was that the current --with-eapi-only
for the Apache compile side doesn't apply the Makefile.tmpl patches
(sslsup.patch), needed to tell Apache --enable-rule=EAPI, and some other
stuff. Linking with libraries for a.out as you mention above similarly may
be a problem. I'll mail you privately once I have a chance to look at it
all.
--
-- Todd Vierling (Personal [EMAIL PROTECTED]; Bus. [EMAIL PROTECTED])
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
