[Patch] Improve diags for "OpenSSL headers match library" configure test

[Ben Lindstrom]

This is extactly what I was thinking.  It will at least let people know
that they truly do have multiple OpenSSL versions co-mingled.  It would be
nice if there was a way to pin point the two deviant versions and let the
user known where he has to clean up, but I think that is asking way too
much.  Maybe a blerb in INSTALL talking about cleaning up multiple OpenSSL
versions and have the failure point to INSTALL's section.

Tim, if you don't have any complaints on it.  It has my blessing.  Since
the upstream tree is down.  I won't be able to commit it more than likely
until I get back from my trip.

- Ben

On Sat, 3 Aug 2002, Darren Tucker wrote:

> Ben Lindstrom wrote:
> > Suggestion.  Can we seperate the tests?
> >
> > OpenSSL header version you have is...<version number>
> > OpenSSL library version you have is..<version number>
> > Error: Header and Library conflict, please check for multiple version
> > installed.
> >
> > Or something like that.
>
> How's this? It's based on the --with-default-path handling as suggested
> by Tim.
>
> Because the header test returns the text description string too, I kept
> the original library/header test. Example output:
>
> checking OpenSSL header version... 90604f (OpenSSL 0.9.6d 9 May 2002)
> checking OpenSSL library version... 90604f (OpenSSL 0.9.6d 9 May 2002)
> checking whether OpenSSL's headers match the library... yes
>
> checking OpenSSL header version... 90604f (OpenSSL 0.9.6d 9 May 2002)
> checking OpenSSL library version... 90602f (OpenSSL 0.9.6b [engine] 9
> Jul 2001)
> checking whether OpenSSL's headers match the library... no
> configure: error: Your OpenSSL headers do not match your library
>
> --
> Darren Tucker (dtucker at zip.com.au)
> GPG Fingerprint D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
>     Good judgement comes with experience. Unfortunately, the experience
> usually comes from bad judgement.