[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Caml-list] [ANN] beta-release of OPAM
> I would suggest that OPAM should always set the variable OCAMLFIND_CONF to > $HOME/.opam/$COMPILER/lib/findlib.conf, so that, whatever the "ocamlfind" > that ocamlbuild uses, it will always use the packages installed by OPAM. I've tried that and unfortunately this didn't seem to work. ocamlfind is picking the wrong compiler. -- Thomas > > Can't this be automatically done by defining the variable in the .opam of > ocamlfind ? > > --Fabrice > > On 01/16/2013 11:01 AM, Anil Madhavapeddy wrote: >> On 15 Jan 2013, at 21:12, Wojciech Meyer <wojciech.meyer@xxxxxxxxx> wrote: >> >>> Roberto Di Cosmo <roberto@xxxxxxxxxxx> writes: >>> >>>> I can confirm this : on opam 0.8.3, this bug prevented me from >>>> compiling properly a test code for Parmap. >>>> It definitely needs to be fixed :-) >>> >>> It's been fixed on trunk now. >> >> Thanks for the quick fix! Looking at the patch, the problem >> seems to be that ocamlbuild distinguishes between built-in tools >> (presumably the ocaml toolchain binaries), and external tools. >> >> Is there any reason why ocamlbuild shouldn't just unconditionally >> search the PATH for the compiler tools as well? It's very confusing >> to have it override some binaries and not others. >> >> -anil >> >
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |