Closed judy-zz closed 9 years ago
Looks like it could be a duplicate of this issue:
I resolved it! As recommended near the bottom of that page, brew link --force openssl
appears to fix it. I'm not sure why or how it works. Other than that, the installation process works beautifully. Maybe add a check to see if the right files are in place, and if not, recommend running that command to the end user? If it can't be fixed within Eve itself?
Thanks for the comments. Even though you resolved it yourself, it's good for us to see some real-world examples of installation issues users are facing. System configuration is tricky for us to solve with a build script, since we don't want to mess with people's environments. In the future we'll have a hosted version and binaries for each platform to ameliorate this kind of issue. In the meantime, I think it's a great idea to start a installation FAQ for people who run into already solved issues.
Thanks for opening this issue. Although your solution didn't work for me, the link you included did point me to something that worked for me.
So, since El Cap 10.11 no longer uses openssl it doesn't include the headers which requires you to install it (in our case via Brew) separately.
So, in addition to installing openssl I also had to export the path to the headers using: export OPENSSL_INCLUDE_DIR=/usr/local/Cellar/openssl/1.0.2d_1/include/ although pointing to a particular release version smells and should probably be export OPENSSL_INCLUDE_DIR=/usr/local/opt/openssl/include
Thanks for the help. I will update the installation FAQ with your tip.
Fresh install of Eve on a MacBook Air (13-inch, Mid 2011) running OS X El Capitan. Homebrew 0.9.5 is installed, along with latest XCode for El Capitan.
./install-multirust.sh
completed with no warnings or errors. Then I run./bash.sh
and get this:Looks like I'm missing openssl header files. Should they be included in the project somewhere? Should I be installing openssl some other way first via Homebrew?