You can force neon to use an old SSL. --with-ssl --with-force-ssl
This is useful on Debian Woody for instance, where the backported the
recent security fixes to SSL to an older version.
TTimo
On 20 Sep 2002 11:19:50 -0500
Ben Collins-Sussman <sussman@collab.net> wrote:
>
> Hey Joe,
>
> I tried to build subversion --with-ssl today for the first time.
> Neon's ./configure kept refusing, because it kept finding older
> openssl headers on my system.
>
> On FreeBSD, I think openssl is part of the core system created by
> 'make world', and these headers are installed in
> /usr/include/openssl/, while the latest *port* of openssl places the
> headers into /usr/local/include/openssl/.
>
> In a nutshell, I couldn't figure out how to make neon use one set of
> headers, and not the other. Is this something fixable? Is it a bogus
> aspect of some autoconf macro that neon is using?
>
> (In the end, I actually had to fake out my system by moving
> /usr/include/openssl away, and making that location a symlink to
> /usr/local/include/openssl/. I'm probably asking for trouble now.)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 20 18:24:53 2002