-
Notifications
You must be signed in to change notification settings - Fork 70
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
Setting OCAMLFIND_DESTDIR
can mess with opam installation
#136
Comments
From your description, it sounds like a problem that can affect all packages that use |
@Alizter what's the actual build failure you're seeing under Nix? It'll help diagnose the issue. |
Here is what opam spits out:
Something in Nix set
unsetting this env var lets the opam command succeed. Here is the out file for the opam build:
|
This issue is not super cirtical for me since I am doing something very nonstandard. Normal users will never touch that env var. I was attempting to quickly set up some opam switches for testing the interaction of opam and Dune. When I actually need different versions of packages I just use Nix anyway. |
|
I'm not sure if this is the correct place to report this, but when installing
zarith
via opam andOCAMLFIND_DESTDIR
has been set (i.e. because of a Nix shell) then opam will inherit the env var which causes the build to fail. This can obviously be worked around by unsetting the env var, but it might be worth reporting it here with the workaround in case anybody else comes across the issue.The text was updated successfully, but these errors were encountered: