From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Peter Halacsy" <peter@halacsy.com>
Cc: "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] 3.10 and native profiling
Date: Sun, 18 Mar 2007 11:01:59 +0100 [thread overview]
Message-ID: <cd67f63a0703180301m41676b5ft6b2a1812f6ba2841@mail.gmail.com> (raw)
In-Reply-To: <9EDCA893-85B5-43A9-A441-EA56CFAA4820@halacsy.com>
On 3/18/07, Peter Halacsy <peter@halacsy.com> wrote:
> hello,
> i've installed 3.10 beta compiler (intel mac). But I can't use the
> native code profiling. I can't compile my code.
[...]
> $ /usr/local/ocaml/10.0/bin/ocamlopt.opt -p test.ml
> Cannot find file std_exit.p.cmx
You certainly used the experimental build (./build/fastworld.sh &&
./build/install.sh), since I've fixed that bug some days ago (the CVS
version should works fine).
--
Nicolas Pouillard
prev parent reply other threads:[~2007-03-18 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 7:54 Peter Halacsy
2007-03-18 10:01 ` Nicolas Pouillard [this message]
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=cd67f63a0703180301m41676b5ft6b2a1812f6ba2841@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=peter@halacsy.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).