[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

neon question

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-09-20 18:19:50 CEST

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
Received on Fri Sep 20 18:21:51 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.