/usr/bin/ar: permission denied when running haste-boot #353
Comments
That's interesting, and slightly weird: Haste should never be calling |
It's called by And I'm pretty sure it's related to this main cabal issue. I have unix 2.7.1.0 installed system-wide, but I suppose haste-cabal is downloaded as a binary and thus might have older version in it. I'll see if I can build just that from source with new EDIT: I hit environment problems while building cabal. Will retry soon and see if getting new |
@bananu7 I've run into the same issue it seems. I tried building cabal from source as stated in the README, and it includes unix 2.7.1.0 when run. But I still get the same error as above. Did you get this working, if so, how? :) Cheers |
It was a while ago; I think that fixing |
Alright, thanks for the lead! :) On Thu, Mar 3, 2016 at 12:45 PM Bartek Banachewicz notifications@github.com
|
Until this is fixed (and even after that - this build is finicky), it's highly recommended that you use the pre-built binaries for non-Linux platforms. Not only does this have a substantially higher likelihood of working, but you also get niceties such as manual pages and not having to wait forever for |
I have downloaded the pre-build Haste binary and am trying to compile https://github.com/yamafaktory/reflex-starter with it.
|
Unfortunately, I don't think using the pre-build binary is a solution, because the haste-cabal that comes with it still doesn't seem to work:
|
Fixed as of release 0.5.5.1. |
So, time to try reflex-frp with haste now? On 16 Oct 2016 4:06 am, "Anton Ekblad" notifications@github.com wrote:
|
I can't run haste-boot after a fresh installation on El Capitan (via cabal). I immediately get "/usr/bin/ar: permission denied", even when running as root. This might be related to the "System Integrity Protection" that Apple introduced in OS X El Capitan.
Edit: Seems to work if one disables SIP before running haste-boot (boot into safe mode and run "csrutil disable"), and then re-enables it again afterwords.
The text was updated successfully, but these errors were encountered: