-
Notifications
You must be signed in to change notification settings - Fork 29
Fails to configure on 10.11 #78
Comments
Aye, we've noticed the same issue here. I haven't had a chance to look into it to see if it's a puppet-php issue or a phpenv one, though. Did you find a resolution for this @jenslind? |
@gblair Also had to do some ugly regex to fix php 5.5 support. As discussed here: https://github.com/Homebrew/homebrew-php/issues/1941 There is probably a better solution to this now. :) |
Thanks! oddhill/puppet-php@82e386d did work for us, too. |
👍 We're most probably seeing this issue as well... |
We're still seeing issues with this, but currently with the above patch I still get stuck with the same error as in here: https://github.com/Homebrew/homebrew-php/issues/1931 |
The suggested fix |
@mattheath any suggestions? :) I'll try a clean install of this next week. |
@hussfelt does this help at all?: castiron/puppet-php@castiron:2a2d9b8020524f8853e526763cf9435e3c9f0816...master Credit to @jenslind for most of that. I believe those were the ∆s we needed to make in order to be able to build PHP in El Cap on our team here. In a nutshell, we ensure that an alternative version of OpenSSL is in place and then use that when compiling PHP. |
@gblair I actually pointed at your repo/version 2.0.107, and now I get even more confused.
Feels that I am missing something obvious? |
Hmmm @hussfelt it looks like |
@gblair I get the same error, but with the 101 version instead. :( |
We had some new people join the team here in recent days, and in provisioning new machines, we ran into the issue of
I chose to include the openssl package in our own repo like this, because if libraries start including it internally, silly conflicts can arise when two different libraries try to install the same package (duplicate resource errors). |
Looks like the openssl headers have been removed from
/usr
in El Capitan.The text was updated successfully, but these errors were encountered: