Re: openssl - could not find the C header files

2015-10-20 Thread Christopher Jones
> Anyway, I gave up compiling it myself and installed tor 0.2.6.9_1 through > MacPorts. > To keep all my stuff I just copied then the tor binary to the previous tor > 0.2.6.6 (git-bb8c4e69ca5c8bca), which I compiled myself before. > > mv /usr/local/bin/tor /usr/local/bin/tor.old > cp /opt/local

Re: openssl - could not find the C header files

2015-10-20 Thread Frank Röhm
> Am 18.10.2015 um 09:44 schrieb Jeremy Huddleston Sequoia > : > > No, OS X does not ship with Libressl. OS X 10.11 ships with OpenSSL 0.9.8zg > at /usr/lib/libssl.0.9.8.dylib and OpenSSL 0.9.7l at > /usr/lib/libssl.0.9.7.dylib. These binaries are present to maintain binary > compatibility.

Re: openssl - could not find the C header files

2015-10-18 Thread Frank Röhm
> Am 18.10.2015 um 09:44 schrieb Jeremy Huddleston Sequoia > : >>> >>> You probably got the system OpenSSL the last time you built it. 10.11 >>> doesn't have OpenSSL any more (I think it has LibreSSL? which is not 100% >>> compatible, apparently). > > No, OS X does not ship with Libressl. OS

Re: openssl - could not find the C header files

2015-10-18 Thread Stephen J. Butler
It looks like tor uses "--with-openssl-dir". There are a couple other packages you might want to install in macports and specify similarly: libevent, zlib, libminiupnpc On Sat, Oct 17, 2015 at 1:44 PM, Brandon Allbery wrote: > On Sat, Oct 17, 2015 at 2:24 PM, Frank Röhm wrote: > >> checking for

Re: openssl - could not find the C header files

2015-10-18 Thread Jeremy Huddleston Sequoia
> On Oct 17, 2015, at 16:00, Frank Röhm wrote: > > >> Am 17.10.2015 um 20:44 schrieb Brandon Allbery : >> >> On Sat, Oct 17, 2015 at 2:24 PM, Frank Röhm wrote: >> checking for openssl directory... configure: WARNING: We found the libraries >> for openssl, but we could not find the C header f

Re: openssl - could not find the C header files

2015-10-18 Thread Ryan Schmidt
On Oct 17, 2015, at 6:00 PM, Frank Röhm wrote: > Yes there still seems to be openssl in 10.11, but old version, OpenSSL > 0.9.8zg 14 July 2015 find I in /usr/bin/openssl > I renamed it to …OLD and linked the macports openssl to this path. > > MacBook:tor-0.2.7.3-rc f$ ls -al /usr/bin/openssl >

Re: openssl - could not find the C header files

2015-10-17 Thread Brandon Allbery
On Sat, Oct 17, 2015 at 7:00 PM, Frank Röhm wrote: > MacBook:tor-0.2.7.3-rc root# ./configure --with-openssl=/opt/local > configure: WARNING: unrecognized options: --with-openssl > I haven't built tor, so I was guessing as to the configure option (I specifically said "or similar"). I suggest "./

Re: openssl - could not find the C header files

2015-10-17 Thread Frank Röhm
> Am 17.10.2015 um 20:44 schrieb Brandon Allbery : > > On Sat, Oct 17, 2015 at 2:24 PM, Frank Röhm wrote: > checking for openssl directory... configure: WARNING: We found the libraries > for openssl, but we could not find the C header files. You may need to > install a devel package. > config

Re: openssl - could not find the C header files

2015-10-17 Thread Ryan Schmidt
It's probably not related to your current problem, but I wanted to point out: On Oct 17, 2015, at 1:24 PM, Frank Röhm wrote: > openssl is installed: > > MacBook:dports root# port list installed > ... > openssl@1.0.2d devel/openssl > … The command you want is "por

Re: openssl - could not find the C header files

2015-10-17 Thread Brandon Allbery
On Sat, Oct 17, 2015 at 2:24 PM, Frank Röhm wrote: > checking for openssl directory... configure: WARNING: We found the > libraries for openssl, but we could not find the C header files. You may > need to install a devel package. > configure: error: Missing headers; unable to proceed. > You pro

openssl - could not find the C header files

2015-10-17 Thread Frank Röhm
Hello one and half a year ago I compiled tor easily “tor” from the original source on my MacBook Pro (2009/11) with at this time still OS 10.6.8 No worries there. Now I want to re-compile the new and actual tor-0.2.7.3-rc source under El Capitan (OS 10.11) but I get errors. I had updated the