Thanks for your reply,
I'll then get the sources for apache 1.3.3 ;-)
But have to disagree with you about the solution you gave for the SSL_BASE
variable. Here is the problem:
(first, I wiped the test for the EAPI flag, otherwise, I cannot get further
;-)
- When I don't set a SSL_BASE variable, I get a 'cannot find SSL
installation in /usr/local/ssl'. That is normal.
- The program that configure is trying to get is 'ssleay'. In Debian, it is
located as file '/usr/bin/ssl/ssleay'.
- If I set SSL_BASE to '/usr/bin/ssl', it will not find it, as the
line you use to test the presence of the ssleay file is:
'if [ -f "$SSL_BASE/bin/ssleay" ]; then ...'
($SSL_BASE/apps/ssleay is tried too)
As you can see, I cannot map /usr/bin/ssl into $SSL_BASE to match
the test !
There are two possible modifications to make it work:
1) Create a link in the /usr/bin/ssl directory named 'bin' that is a link
to the directory where it is (/usr/bin/ssl/bin will point to /usr/bin/ssl
;-)
2) Modify all the references in libssl.module to allow such mapping (that
makes 3 lines modified).
I think the easyest is the first solution. It would be cool to write to the
debian maintainer of the ssleay package to add such link in his package.
BUT:
There's the same problem with the include files from ssleay-dev. They are
located in a complete different location from the binary part of ssleay (
they are in /usr/include/ssl). The problem is that the same variable is
used
(BASE_SSL) to point for binary and include files ;-(
So if I put '/usr/bin/ssl' in BASE_SSL, it will look in
/usr/bin/ssl/include for the include files ;-(
I've no solution for this, except modifying the libssl.module file.
Thanks,
Luc Stepniewski
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
