From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 6D88D7EEEF for ; Tue, 23 Jun 2015 19:45:23 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of kennethadammiller@gmail.com) identity=pra; client-ip=209.85.218.51; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="kennethadammiller@gmail.com"; x-sender="kennethadammiller@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of kennethadammiller@gmail.com designates 209.85.218.51 as permitted sender) identity=mailfrom; client-ip=209.85.218.51; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="kennethadammiller@gmail.com"; x-sender="kennethadammiller@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-oi0-f51.google.com) identity=helo; client-ip=209.85.218.51; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="kennethadammiller@gmail.com"; x-sender="postmaster@mail-oi0-f51.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BhAwC6molVlTPaVdFbgkWBfgaDGKl8hg+TcwdMAQEBAQEBEgEBAQEHDQkJHzCEOxEdARseAxIDDTcCJAERAQUBIjWHdwEDEpkWjTqDMT4xiz+Ba4J5iysKGScNV4U2AQUOkzGBQwWTf4cvhCKWaxIjgQwJF4QlIjGCSAEBAQ X-IPAS-Result: A0BhAwC6molVlTPaVdFbgkWBfgaDGKl8hg+TcwdMAQEBAQEBEgEBAQEHDQkJHzCEOxEdARseAxIDDTcCJAERAQUBIjWHdwEDEpkWjTqDMT4xiz+Ba4J5iysKGScNV4U2AQUOkzGBQwWTf4cvhCKWaxIjgQwJF4QlIjGCSAEBAQ X-IronPort-AV: E=Sophos;i="5.13,666,1427752800"; d="scan'208";a="166912592" Received: from mail-oi0-f51.google.com ([209.85.218.51]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 23 Jun 2015 19:45:22 +0200 Received: by oigb199 with SMTP id b199so12479035oig.3 for ; Tue, 23 Jun 2015 10:45:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=0l4DKxyGSo0OhIxyxfE9nW1nlhZqGJjSjP7qNFwqc1s=; b=vCCy0Mophnwi7NEW5WYAY8qqyBGLue3gPBDWrFhFRtnzwQRZ1Ip07+VW0ixTm9Qag3 8h54WyuK1NzjE+pFJIX/+n/uRdqYYyWvUP46Dv7hZIuO9GVSuZAxkLJWMIRNRamfPR5w o+xi1bsity9hoLWlsaiV4ie2DYMfiowK90f4BdrnyZFfB7eNfr9J0qmy7qU4gBxXcxNQ P93aKLq/MmWAeKTbvRBC9+4PZLEibX1mne5Dc14piDM55hu1+mWRkXGVSL1/Fmi2aZHR bw/Jt/Zt+D+Qo0pWy46Cw3HzqkZ4r/M9gN20tFyJcK+h//m7s+81vTJK/gSZKnx7pPYw lLhw== MIME-Version: 1.0 X-Received: by 10.182.87.137 with SMTP id ay9mr30646532obb.68.1435081521346; Tue, 23 Jun 2015 10:45:21 -0700 (PDT) Received: by 10.202.191.8 with HTTP; Tue, 23 Jun 2015 10:45:20 -0700 (PDT) Date: Tue, 23 Jun 2015 13:45:20 -0400 Message-ID: From: Kenneth Adam Miller To: caml users Content-Type: multipart/alternative; boundary=089e0111c01a4dbe80051932f4d4 Subject: [Caml-list] Library Compile Error --089e0111c01a4dbe80051932f4d4 Content-Type: text/plain; charset=UTF-8 I'm using OCamlMakefile (rather the library that I'm editing uses it, and I have to use it consequently), and I need to add some package dependencies in order to recompile each while developing locally before I ship my changes to opam. Basically, I've added the core and core_kernel packages to these libraries to make some functions tail recursive. But it's turning out that using OCamlMakefile has made it more difficult than it sounds. A is consumed by B, but both must be installed for them to be usable on the target machine. Currently, you can do an opam install A B and it will work. A has been successfully edited and subsequently recompiled to consume core and core_kernel as it needs to. I was even able to opam pin the package to get it working locally. B consumes A, but weirdly, B complains of the following when I try to make it: Error: No implementations provided for the following modules: Core_kernel referenced from /path/to/(A) Core referenced from /path/to/(A) I noted that in Stack Overflow that there were some issues with casing for package names when you built stuff. This is strange because when I was compiling A, it worked fine. I changed the casing to A instead of a in the OCamlMakefile export PACKS= line, and it failed, unable to find the package A. So, A compiles just fine, but B refuses. I tried to change B to specify various combinations of casing of core (as in: PACKS+=core vs PACKS+=Core) but that failed too. So now I don't know how to get B to compile using OCamlMakefile. --089e0111c01a4dbe80051932f4d4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm using OCamlMakefile (rather the library that I'm editing= uses it, and I have to use it consequently), and I need to add some packag= e dependencies in order to recompile each while developing locally before I= ship my changes to opam. Basically, I've added the core and core_kerne= l packages to these libraries to make some functions tail recursive. But it= 's turning out that using OCamlMakefile has made it more difficult than= it sounds.

A is consumed by B, but both must be installed for them to be usable= on the target machine. Currently, you can do an opam install A B and it wi= ll work.=C2=A0 A has been successfully edited and subsequently recompiled t= o consume core and core_kernel as it needs to. I was even able to opam pin = the package to get it working locally.

B consumes A, but weirdly, B complains of= the following when I try to make it:

Error: No implementations provi= ded for the following modules:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Core= _kernel referenced from /path/to/(A)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0Core referenced from /path/to/(A)

I noted that in Stack= Overflow that there were some issues with casing for package names when yo= u built stuff. This is strange because when I was compiling A, it worked fi= ne. I changed the casing to A instead of a in the OCamlMakefile export PACK= S=3D line, and it failed, unable to find the package A.

<= div id=3D"yiv2029449846yui_3_16_0_1_1434145276039_382075" dir=3D"ltr" class= =3D"" style=3D"color:rgb(0,0,0);font-family:HelveticaNeue,'Helvetica Ne= ue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:16px">= So, A compiles just fine, but B refuses. I tried to change B to specify var= ious combinations of casing of core (as in: PACKS+=3Dcore vs PACKS+=3DCore)= but that failed too.=C2=A0

So now I don't know how to= get B to compile using OCamlMakefile.

--089e0111c01a4dbe80051932f4d4--