Maybe the autoconf script is looking at the headers in /usr/include, instead of /usr/local/include ? That would mess it up. Instead of using --with-openssl-dir=/usr/local, what happens if you set CFLAGS and LDFLAGS by hand when compiling?
I tried to find out how to do this by myself but I don't understand very well how these flags work.
Could you please provide some examples and I'll test?Also of note, I was able to get tor-0.2.6.2-alpha to build succesfully on a the release version of OpenBSD 5.6 which includes LibreSSL 2.0-something.
When I tried to build tor-0.2.6.2-alpha against libressl 2.1.2 on the same system using ./configure --with-openssl-dir=/usr/local it bails out with same the tortls.o error.
For the meantime, is there a compiler macro we can use to distinguish libressl from openssl at compile-time?
Do not know. _______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays