From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id C8D0A7ED7A for ; Mon, 1 Oct 2012 06:40:46 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of lambda.q.q@gmail.com) identity=pra; client-ip=209.85.220.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="lambda.q.q@gmail.com"; x-sender="lambda.q.q@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of lambda.q.q@gmail.com designates 209.85.220.182 as permitted sender) identity=mailfrom; client-ip=209.85.220.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="lambda.q.q@gmail.com"; x-sender="lambda.q.q@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-vc0-f182.google.com) identity=helo; client-ip=209.85.220.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="lambda.q.q@gmail.com"; x-sender="postmaster@mail-vc0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Am0BAHweaVDRVdy2kWdsb2JhbABFrGiIawGIXQgjAQEBAQkJDQcSKYIXIgIsATkDDQUIAQddEgEFASIbGodRAw+ZDIJhCQOPGoQ+Jw2JTgEFDIsYhkYDiFKFMIdngRWKDYMqFimBVoI2 X-IronPort-AV: E=Sophos;i="4.80,514,1344204000"; d="scan'208";a="175204923" Received: from mail-vc0-f182.google.com ([209.85.220.182]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 01 Oct 2012 06:40:46 +0200 Received: by vcbfw7 with SMTP id fw7so9305251vcb.27 for ; Sun, 30 Sep 2012 21:40:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=oFftpPHpmQQe8EcvA0yO3tLaJMfcLxE+zlSmEYYDHRw=; b=Z0tm7w3H01bpM/tuC308EUGIrJjAy1zkBOOx5W7vAVi0ED27OTuPHxIULk9X39fzb0 Y58TsqZ+7RF65pQF+ZfXQh9YXTkDwL8tnytjNIfO78Cv6XRp3MktLbA7sYn7wtN1gwLc k45oBH7f/4zLe3OVs0npIaSElaIEfqhHRJYJmLbE4Rk4mFu60s5N+n+UTjfX1/EQPXih w1wBjOEvdqVGngN7TgNcB02VPO3sqPqmT80V0uQgQM5WCJSBAGVJsxm1m6v52X/Cm5Xg bouF5BSXyc3w0uU+vClb6qRBBqn+2diVahx6vqC0BF1FE4Erqlv7blMs2rZelOPbMp4A X62Q== MIME-Version: 1.0 Received: by 10.58.79.178 with SMTP id k18mr8086021vex.3.1349066444905; Sun, 30 Sep 2012 21:40:44 -0700 (PDT) Sender: lambda.q.q@gmail.com Received: by 10.59.7.166 with HTTP; Sun, 30 Sep 2012 21:40:44 -0700 (PDT) Date: Mon, 1 Oct 2012 08:40:44 +0400 X-Google-Sender-Auth: aZapbMT-hsLUV2XttMQlK9EtNCY Message-ID: From: Ivan To: caml-list Content-Type: multipart/alternative; boundary=047d7b5da23d3a1e1604caf80285 Subject: [Caml-list] using typerex with ocamlfind enabled ocamlbuild (ocaml 3.11.2) --047d7b5da23d3a1e1604caf80285 Content-Type: text/plain; charset=ISO-8859-1 I'am using ocaml 3.11 and want to use ocamlbuild, batteries and typerex. I've downloaded ocamlfind enabled myocamlbuild.ml. But, it seems, that there is no opportunity to include support of typerex without breaking support for ocamlfind. So, I've tried to edit my /etc/ocamlfind.conf, or to specify an environment variable: OCAMLFIND_COMMANDS to 'ocamlc=ocp-ocamlc' but neither works. It seems that myocamlbuild overrides this setups. Please, can anybody help me to solve this. Or, maybe, there is a better way to use batteries and typerex? --047d7b5da23d3a1e1604caf80285 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'am using ocaml 3.11 and want to use ocamlbuild, batteries and typerex= .
I've downloaded ocamlfind enabled myocamlbuild.ml. But, it seems, that there is no=A0opportunity=A0to= include support of typerex without breaking support for ocamlfind.
So, I've tried to edit my /etc/ocamlfind.conf, or to specify an en= vironment variable:=A0=A0OCAMLFIND_COMMANDS to 'ocamlc=3Docp-ocamlc'= ; but neither works. It seems that myocamlbuild overrides this setups.

Please, can anybody help me to solve this. Or, maybe, there = is a better way to use batteries and typerex?
--047d7b5da23d3a1e1604caf80285--