-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
First-time OS X users hit FUSE error during standard go install procedure #595
Comments
good find, this is super annoying for our poor users. relevant discussion on irc starting at https://botbot.me/freenode/ipfs/2015-01-18/?msg=29902881&page=5 |
@jbenet This is alpha priority, yeah? (trying to make sure all alpha relevant issues/PRs are marked under the milestone) |
Yeah i think so. what was the approach we settled on? |
Yeah, we decided we wanted to make go-fuse-version a separate binary, and when you try to mount on OSX, it would check for the binary, and prompt the user to install it if missing. Once the binary is present, we just exec it to see if the user has a compatible version of fuse installed |
we can probably install it as part of |
A couple caveats with that, Its only required on OSX, and it requires the user have the proper FUSE headers installed. |
make it part of |
This was fixed in 7ae3706 |
Hi, I've run into this same error today:
It looks as though the same error occurred when using
So, I've installed osxfuse to fix this:
(from #177) Now, I don't get the errors, but
:/ |
The issue is fixed by installing FUSE
Either ...
a) instruct users to install FUSE first
b) remove the need for FUSE on go install
c) Is there another way to satisfy the need for the headers without having FUSE installed? (is this a sensible question?)
The text was updated successfully, but these errors were encountered: