-
Notifications
You must be signed in to change notification settings - Fork 349
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 init complains that sandboxing isn't working on platform macports #4368
Comments
This was a bug in the first beta, should be fixed in 2.1.0~beta2 |
@AltGr The behavior i reported was seen with both 2.1.0~beta2 and with a version compiled from opam-trunk after the beta2 was released. |
Yes, the variable ( For depext / macports issues, there is an open one, about variants and their handling #4297. If it is nt the same problem, feel free to open a new one, like that we can investigate on it. |
Hi,
I'm trying to use the opam 2.1 beta version (I tried both the published beta, and a version compiled from the current trunk) with a clean install. When I run
opam init
I see an error message about sandboxing not working.If I ignore the warning and continue by pressing
N
the install seems to succeed without issues. (opam doesn't automatically source the correct switch for me anymore even though the shell hooks have been installed, but the install overall seems to work fine).I am using macOS 10.15 (Catalina) along with macports. This error wasn't present in the opam 2.0 series.
I'm wondering if this is an environment variable issue and I need to setup something to let Opam know about macports? It seems like the new depext integration is also having trouble finding dependencies like libffi via macports. It complains about them not being installed even though they are.
The text was updated successfully, but these errors were encountered: