Right. This is part of my confusion here. I've looked at the logic, I even
posted it to show what it's trying to do. It's obvious that withval is
getting set to yes. Not sure why, and supplying a path to openssl hasn't
solved anything as yet, except to give me an even more ridiculous error.
I'm going to do my usual punnet and see if that works. I'll report status
as soon as I'm done.
--
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
On Mon, 9 Apr 2001, Jim Winstead wrote:
> On Mon, Apr 09, 2001 at 02:44:50PM -0700, [EMAIL PROTECTED] wrote:
> > > So the question here is what should withval be set to or how should it be
> > > used. When I change the $withval/openssl/ssl.h to
> > > /usr/include/openssl/ssl.h then everything works and it reports:
> > >
> > > checking for SSL library... checking whether to enable mod_tls... yes
> > > found OpenSSL
> > >
> > > Anyone?
> >
> > You should be using --with-ssl=/path/to/openssl. This argument is used to
> > find your SSL header files. If you do not provide a path, we can not find
> > them.
>
> the modules/tls/config.m4 logic here strikes me as quite bogus. what
> is the path being supplied? it peers into a number of subdirectories
> to find the header files, but assumes the libraries are in the
> supplied directory.
>
> it should also either try to guess the path or bail when just
> --with-ssl is used. the current behavior (using 'yes' as the path)
> is more than a little confusing.
>
> i'm not familiar enough with how openssl is installed (by default
> or by various distributions) to know what the right thing to do is,
> but on a debian system, the libraries are in /usr/lib and the
> headers in /usr/include/openssl. if a read the current config.m4
> right, i would supply --with-ssl=/usr/include, and a -L/usr/include
> would get added to the link flags. that's obviously wrong.
>
> jim
>
