-
Notifications
You must be signed in to change notification settings - Fork 3
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
opam install sibylfs
fails
#14
Comments
Thanks for the bug report. Yes, this is the problem with opam approaches. Hopefully the nix install works fine? @dsheets can you make the fixes? |
I might look further into it (e.g. Nix) once these syscalls are implemented in 'Windows Subsystem for Linux':
Would be neat to check their POSIX filesystem conformance :P |
Ah! You are running on windows via some kind of ubuntu compatibility layer on top of windows? Yes, mount you can probably work around. And also chroot. But for obvious reasons be careful if you omit chroot! |
I've fixed the pinning It would indeed be neat to check WSL's POSIX conformance but I'm afraid it's probably too incomplete and unstable at this time. I appreciate your trying to get this to work and your report regarding missing dependency constraints. Please, let us know if you encounter other issues. |
Be sure to note that you are not supposed to make any changes for WSL if something works on Linux. Microsoft ought to take care of missing functionality. Though maybe the case of missing chroot() could be looked into. Possibly a "soft-chroot" where all the traces proveably don't go outside a certain path could be neat for running SibylFS on even dumber OSes. |
If you do get it to work, it would be very interesting to see the results! We can post them on the sibylfs.io website also. |
|
How to get it installed, on Ubuntu 14.04:
I had this github repo pinned in opam.
As a user you probably want to
opam pin add <pkg> <version>
all of those, to not run into problems withopam upgrade
or later package installations,Reasons:
The last three items can probably be fixed on your end.
The text was updated successfully, but these errors were encountered: