From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Alain Frisch <alain@frisch.fr>
Cc: caml-list <caml-list@inria.fr>,
wg-camlp4@lists.ocaml.org, Leo P White <lpw25@cam.ac.uk>,
Anil Madhavapeddy <avsm2@cl.cam.ac.uk>
Subject: Re: [Caml-list] Working Group: the future of syntax extensions in OCaml, after camlp4
Date: Thu, 24 Jan 2013 16:57:37 +0100 [thread overview]
Message-ID: <90C5BC201F264C4C902B4E7897660042@erratique.ch> (raw)
In-Reply-To: <510145A5.6030807@frisch.fr>
Le jeudi, 24 janvier 2013 à 15:31, Alain Frisch a écrit :
> - Gather information from the community about the use of camlp4.
> (Please consider sharing information about your use of camlp4
> and camlp4-based extensions, even if you don't plan to participate
> to the working group discussions!)
I tried to disable camlp4 to compile OCaml 4.00.1 on a raspberry pi --- takes half the (long) compilation time, and allows you to compile OCaml without having to increase the swap size of the default raspbian image to prevent the system from crashing during camlp4 compilation...
However one thing I learned is that currently, it's pretty a no go as camlp4 is needed by ocamlfind which means that if you use something like opam to install software you can't install any of the 'required by' packages mentioned on this page [1].
So it seems that to get rid of camlp4, ocamlfind needs to get rid of camlp4, I'd be interested in what Gerd has to say about that (I have no idea if camlp4 is used by the tool itself or if it's just needed to provide support for camlp4).
Best,
Daniel
[1] http://opam.ocamlpro.com/pkg/ocamlfind.1.3.3.html
next prev parent reply other threads:[~2013-01-24 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 14:31 Alain Frisch
2013-01-24 15:52 ` Török Edwin
2013-01-24 15:56 ` Ashish Agarwal
2013-01-24 16:03 ` Esther Baruk
2013-01-24 15:57 ` Daniel Bünzli [this message]
2013-01-24 16:24 ` AW: " Gerd Stolpmann
2013-01-28 12:15 ` Alain Frisch
2013-01-28 12:17 ` [wg-camlp4] " Alain Frisch
2013-02-03 14:01 ` AW: " Jon Harrop
2013-02-03 14:38 ` Simon Cruanes
2013-01-24 16:16 ` rixed
2013-01-24 17:08 ` Alain Frisch
2013-01-24 18:06 ` Jacques Carette
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=90C5BC201F264C4C902B4E7897660042@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=alain@frisch.fr \
--cc=avsm2@cl.cam.ac.uk \
--cc=caml-list@inria.fr \
--cc=lpw25@cam.ac.uk \
--cc=wg-camlp4@lists.ocaml.org \
/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).