From: Thomas Gazagnaire <thomas@ocamlpro.com>
To: Fabrice Le Fessant <fabrissimo@gmail.com>
Cc: Anil Madhavapeddy <anil@recoil.org>,
OCaml mailing-list <caml-list@inria.fr>,
Mirage List <cl-mirage@lists.cam.ac.uk>,
Wojciech Meyer <wojciech.meyer@gmail.com>
Subject: Re: [Caml-list] [ANN] beta-release of OPAM
Date: Wed, 16 Jan 2013 17:40:08 +0000 [thread overview]
Message-ID: <AA877059-B924-4F61-9A7C-5DE02C79E17B@ocamlpro.com> (raw)
In-Reply-To: <50F6E2E9.5020305@gmail.com>
> 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@gmail.com> wrote:
>>
>>> Roberto Di Cosmo <roberto@dicosmo.org> 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
>>
>
next prev parent reply other threads:[~2013-01-16 17:40 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 15:40 Thomas Gazagnaire
2013-01-15 15:42 ` [Caml-list] " Anil Madhavapeddy
2013-01-15 16:17 ` Thomas Gazagnaire
2013-01-15 19:18 ` Alan Schmitt
2013-01-15 19:25 ` Fabrice Le Fessant
2013-01-15 19:29 ` Anil Madhavapeddy
2013-01-15 19:45 ` Roberto Di Cosmo
2013-01-15 21:12 ` Wojciech Meyer
2013-01-16 10:01 ` [Caml-list] " Anil Madhavapeddy
2013-01-16 10:08 ` Wojciech Meyer
2013-01-16 12:13 ` Gabriel Scherer
2013-01-16 14:43 ` Wojciech Meyer
2013-01-16 14:50 ` Gabriel Scherer
2013-01-16 17:27 ` Fabrice Le Fessant
2013-01-16 17:40 ` Thomas Gazagnaire [this message]
2013-01-16 17:46 ` Fabrice Le Fessant
2013-01-16 20:22 ` Roberto Di Cosmo
2013-01-15 20:02 ` [Caml-list] " Daniel Bünzli
2013-01-15 22:16 ` Thomas Gazagnaire
2013-01-15 17:45 ` [Caml-list] " Daniel Bünzli
2013-01-17 7:52 ` [Caml-list] " Sylvain Le Gall
2013-01-16 16:54 ` [Caml-list] " Mike Lin
2013-01-16 17:29 ` Daniel Bünzli
2013-01-17 17:15 ` Alain Frisch
2013-01-17 17:22 ` Anil Madhavapeddy
2013-01-18 10:31 ` Alain Frisch
2013-01-18 10:42 ` Anil Madhavapeddy
2013-01-18 10:46 ` Fabrice Le Fessant
2013-01-22 15:57 ` Thomas Gazagnaire
2013-01-18 11:19 ` Alain Frisch
2013-01-18 11:27 ` Anil Madhavapeddy
2013-01-18 16:23 ` Opam package publication (was Re: [Caml-list] [ANN] beta-release of OPAM) Daniel Bünzli
2013-01-19 9:07 ` Philippe Veber
2013-01-19 10:40 ` Daniel Bünzli
2013-01-22 15:46 ` Thomas Gazagnaire
2013-01-22 16:23 ` Daniel Bünzli
2013-01-22 16:48 ` Thomas Gazagnaire
2013-01-22 17:05 ` Daniel Bünzli
2013-01-22 16:35 ` Alain Frisch
2013-01-22 16:50 ` Fabrice Le Fessant
2013-01-22 16:53 ` Thomas Gazagnaire
2013-01-22 16:59 ` Daniel Bünzli
2013-01-22 18:03 ` Anil Madhavapeddy
2013-01-17 19:33 ` [Caml-list] Re: [ANN] beta-release of OPAM Hongbo Zhang
2013-01-18 12:18 ` [Caml-list] " aditya siram
2013-01-18 18:23 ` Thomas Gazagnaire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AA877059-B924-4F61-9A7C-5DE02C79E17B@ocamlpro.com \
--to=thomas@ocamlpro.com \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=cl-mirage@lists.cam.ac.uk \
--cc=fabrissimo@gmail.com \
--cc=wojciech.meyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).