|Re: core + opam (Resolved)||Sean McLaughlin||9/15/12 1:53 PM|
I didn't realize you need to call
eval `opam config -env`
before every compilation. This fixed the problem. Sorry for the noise.
|Re: core + opam (Resolved)||Yaron Minsky||9/15/12 6:44 PM|
No problem. You should really just put that into your bashrc...
|Re: core + opam (Resolved)||David House||9/16/12 11:18 AM|
I also think opam could offer to do this for you.
|Re: core + opam (Resolved)||Anil Madhavapeddy||9/16/12 11:21 AM|
OPAM can't do the shell eval automatically.
However, there is a bug here anyway. All of the shells invoked by OPAM
(including the builds of the packages) should have the correct environment
variables set, so it's very odd that CAML_LD_LIBRARY_PATH appears to be
incorrect. You shouldn't need to run the eval for opam invocations: only for
using the OCaml environment outside of OPAM.
What OPAM version are you using?
|Re: core + opam (Resolved)||David House||9/16/12 11:30 AM|
On 16 September 2012 19:21, Anil Madhavapeddy <an...@recoil.org> wrote:I mean, it could offer to edit your bashrc for you. Every little helps... :)
|Re: core + opam (Resolved)||Anil Madhavapeddy||9/16/12 11:51 AM|
You should see my bashrc. No machine could edit that :-)
This is indeed a good thing for opam init to suggest (and remove the "would you like to install crucial base packages that will cause odd errors if you select N") prompt that it currently offers.
On github as https://github.com/OCamlPro/opam/issues/151