-
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
problem with lambda-term/lwt #275
Comments
It looks like "ocamlfind" is just used to install the package, but fails because it cannot find "lwt.unix". I think "lwt.unix" is supposed to be installed automatically by lwt, as long as the "base-unix" optional dependency is present (but it is supposed to be provided by the compiler, so it should be present on your system). Maybe you can check whether -enable-unix is present when re-installing lwt ? |
Try |
I tried, and this happened:
|
For some reason, all your base packages are missing. This error is due to It's easily fixed by |
Yeah, that fixed it. Don't know where the problem came from, though. On Fri, Nov 2, 2012 at 8:44 PM, Anil Madhavapeddy
|
I don't know where the problem came from (something went wrong during the installation of base packages apparently), but for sure opam should not let the user in a inconsistent state as you were. So I've pushed a fix to roll-back to the current switch (and delete the new one) in case something go wrong when installing the base packages. |
I faced the same problem today. Just like Ron had. base-* were not marked installed. I guess some opam (I use 0.8.1) forgot to add base-* when it is updated by opam upgrade opam? |
the more than I though, the more than I think than updating opam through opam is a finally not a so good idea. I guess it easier to just warm the user that its opam version is not up-to-date and let him install a newer version at the right place (ie. /usr/local/bin/opam). I'm reopening the issue to double-check the code which install the base packages to see what could have gone wrong there. |
@camlspotter did you get this error after reinstalling a compiler or just after upgrading opam ? |
Sorry but I do not remember well what happend. But probably because I went between opam 0.7.x and 0.8.1. Here is what I did roughly:
So the issue might be caused by multiple versions of opam. In this situation I imagine anything strange could happen... |
I had a quick look at this and I haven't found any clear cause. I'm pushing this to post-beta (ie. 1.0). |
I've added some safety checks which should detect if some base packages are not installed and warm the user. Hopefully this situation will not happen again, so closing this issue. |
I am seeing this error today on OS X 10.9.1, opam 1.1.0.
|
This seems to be an issue with ocamlfind ; |
My install is in a weird situation. Installing of lambda-term doesn't
work, for reasons that are not obvious to me.
The text was updated successfully, but these errors were encountered: