From: whitequark <whitequark@whitequark.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml release 4.03.0
Date: Wed, 04 May 2016 08:29:13 +0300 [thread overview]
Message-ID: <7ca407de3b2707cc7f5fa71a35374392@whitequark.org> (raw)
In-Reply-To: <20160504052119.GA3707@pema>
On 2016-05-04 08:21, Sébastien Hinderer wrote:
> Hi Christophe,
>
> Christophe Raffalli (2016/05/04 03:43 +0200):
>> Thanks for the link ... I saw that gles3 is broken because gcc does
>> not find caml/misc.h ...
>> I probably miss a -I for C stubs ... What is the correct way to get
>> the location of C stub ?
>>
>> I think `ocamlfind printconf stdlib`/caml should work ... But It does
>> not look great ?
>
> Would `ocamlc -where`/caml help?
Please, `ocamlfind ocamlc -where`/caml. This helps with cross-compiling
because
ocamlfind respects the OCAMLFIND_TOOLCHAIN environment variable.
--
whitequark
next prev parent reply other threads:[~2016-05-04 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 19:35 Damien Doligez
2016-04-27 12:01 ` Fabrice Le Fessant
2016-04-27 12:09 ` Francois Berenger
2016-05-04 1:43 ` Christophe Raffalli
2016-05-04 5:21 ` Sébastien Hinderer
2016-05-04 5:29 ` whitequark [this message]
2016-05-04 11:49 ` Hendrik Boom
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=7ca407de3b2707cc7f5fa71a35374392@whitequark.org \
--to=whitequark@whitequark.org \
--cc=caml-list@inria.fr \
/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).