New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/usr/bin/ar: permission denied when running haste-boot #353

Closed
simonjrp opened this Issue Dec 7, 2015 · 10 comments

Comments

Projects
None yet
6 participants
@simonjrp
Copy link

simonjrp commented Dec 7, 2015

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.

@valderman

This comment has been minimized.

Copy link
Owner

valderman commented Dec 19, 2015

That's interesting, and slightly weird: Haste should never be calling ar. Does your .cabal/config contain shared: True or any other interesting flags? This seems like it may be related to, or at least the same kind of problem as, #348.

@bananu7

This comment has been minimized.

Copy link

bananu7 commented Dec 19, 2015

It's called by haste-boot which calls haste-cabal which tries to call ar. I can, sadly, reproduce. No shared: True.

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 unix.

EDIT: I hit environment problems while building cabal. Will retry soon and see if getting new unix in fixes it. I am pretty sure it will.

@atamon

This comment has been minimized.

Copy link

atamon commented Mar 3, 2016

@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

@bananu7

This comment has been minimized.

Copy link

bananu7 commented Mar 3, 2016

It was a while ago; I think that fixing unix got it to work though.

@atamon

This comment has been minimized.

Copy link

atamon commented Mar 3, 2016

Alright, thanks for the lead! :)

On Thu, Mar 3, 2016 at 12:45 PM Bartek Banachewicz notifications@github.com
wrote:

It was a while ago; I think that fixing unix got it to work though.


Reply to this email directly or view it on GitHub
#353 (comment)
.

@valderman

This comment has been minimized.

Copy link
Owner

valderman commented Mar 3, 2016

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 haste-boot to complete.

@saurabhnanda

This comment has been minimized.

Copy link

saurabhnanda commented Aug 22, 2016

I have downloaded the pre-build Haste binary and am trying to compile https://github.com/yamafaktory/reflex-starter with it.

  • haste-cabal init worked
  • haste-cabal install is throwing a /usr/bin/ar: permission denied
@vilhelms

This comment has been minimized.

Copy link

vilhelms commented Oct 2, 2016

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:

$ haste-cabal install parsec
haste-cabal: /usr/bin/ar: permission denied
@valderman

This comment has been minimized.

Copy link
Owner

valderman commented Oct 15, 2016

Fixed as of release 0.5.5.1.

@valderman valderman closed this Oct 15, 2016

@saurabhnanda

This comment has been minimized.

Copy link

saurabhnanda commented Oct 16, 2016

So, time to try reflex-frp with haste now?

On 16 Oct 2016 4:06 am, "Anton Ekblad" notifications@github.com wrote:

Fixed as of release 0.5.5.1.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#353 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABu0W63w0Shuwtdnoo816D15x-nTh3oks5q0VV4gaJpZM4Gv6g-
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment