From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr 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 2D1FF7EE20 for ; Mon, 12 Nov 2012 16:33:16 +0100 (CET) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of agarwal1975@gmail.com) identity=pra; client-ip=209.85.219.54; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of agarwal1975@gmail.com designates 209.85.219.54 as permitted sender) identity=mailfrom; client-ip=209.85.219.54; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="agarwal1975@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-oa0-f54.google.com) identity=helo; client-ip=209.85.219.54; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="agarwal1975@gmail.com"; x-sender="postmaster@mail-oa0-f54.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlQFACQWoVDRVds2m2dsb2JhbABEiHm4IoE4A3oIIwEBAQEBCAkLCRQngmUBGx4DEgkHXQERAQUBFgyICgEDDwuZAYJvjDKCeIREChknDVmIdQEBBAyMdIVfA4hajSKOYhYpglCBXw X-IronPort-AV: E=Sophos;i="4.80,762,1344204000"; d="scan'208";a="181153233" Received: from mail-oa0-f54.google.com ([209.85.219.54]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 12 Nov 2012 16:33:15 +0100 Received: by mail-oa0-f54.google.com with SMTP id n9so10667813oag.27 for ; Mon, 12 Nov 2012 07:33:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=06mrtryhOYdNUYl3b24uAIgie+ycpImUaa0njTYeoYo=; b=Zmxgqz8aPNz3yLeBMZR3fdfh8vR8A547psX4D3ZTiKaRpB0AkpyUV4yxCEBNZQx7eM WzInCG+i9Xz36615HbleHJ/b2xnkDQAMb6zZiL7dM5Rdi+DggDjF9TbIENSnr4R9cPjX 62u5p5fZYT8IlbFNhaMHhaEimQ4T5oJX/TKnfCEiW6041X3BiSsxnvr/k0RM0Gcet/rO CGEX29N0PoZyZWsEq+0FmVvZ6hDtJEZiE9ui6LrrhL8/ZQwLab+I4YzeUcUR/SB5PrM9 32aiw4z71wIC4wZGt4zTBNY65QO1pi5dUPh2M8WPN21csygpHWltvSoC6w6gU2TZ1rym 8cKA== Received: by 10.60.6.227 with SMTP id e3mr12275012oea.22.1352734394191; Mon, 12 Nov 2012 07:33:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.174.101 with HTTP; Mon, 12 Nov 2012 07:32:53 -0800 (PST) From: Ashish Agarwal Date: Mon, 12 Nov 2012 10:32:53 -0500 Message-ID: To: Caml List Content-Type: multipart/alternative; boundary=e89a8fb1f7ee0a8efb04ce4e056a Subject: [Caml-list] opam install seems not to run build command --e89a8fb1f7ee0a8efb04ce4e056a Content-Type: text/plain; charset=ISO-8859-1 We are running opam with a custom repo [1] that includes an oclosure package. Doing `opam install oclosure` fails immediately with: The following actions will be performed: - install oclosure.0-dev 1 to install | 0 to reinstall | 0 to upgrade | 0 to downgrade | 0 to remove =-=-= oclosure.0-dev =-=-= The archive for oclosure.0-dev is in the local cache. Extracting /Users/ashish/.opam/archives/oclosure.0-dev+opam.tar.gz Build commands: configure --prefix /Users/ashish/.opam/system make make install Uninstalling oclosure.0-dev [WARNING] Command "rm -f" contains 1 space The compilation of oclosure.0-dev failed in /Users/ashish/.opam/system/build/oclosure.0-dev. [ERROR] while installing oclosure.0-dev = [RUN] "configure --prefix /Users/ashish/.opam/system" = [CWD] "/Users/ashish/.opam/system/build/oclosure.0-dev" ... lots more environment variables printed However, manually cd'ing to /Users/ashish/.opam/system/build/oclosure.0-dev, then running the configure, make, commands behaves differently. The configure succeeds. The make runs for a while (but I did not let it run to completion). Question is what is opam doing differently then running the commands manually? Is there some way to see the error messages when opam install fails? Also, note this failure happens on Mac OS X but the same repo succeeds for us on CentOS and Ubuntu. [1] https://github.com/smondet/opam-repository --e89a8fb1f7ee0a8efb04ce4e056a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable We are running opam with a custom repo [1] that includes an oclosure packag= e. Doing `opam install oclosure` fails immediately with:

The following actions will be performed:
=A0- install oclos= ure.0-dev
1 to install | 0 to reinstall | 0 to upgrade | 0 to downgrade | 0 to r= emove

=3D-=3D-=3D oclosure.0-dev =3D-=3D-=3D
=
The archive for oclosure.0-dev is in the local cache.
Extrac= ting /Users/ashish/.opam/archives/oclosure.0-dev+opam.tar.gz
Build commands:
=A0 configure --prefix /Users/ashish/.opam/s= ystem
=A0 make
=A0 make install
Uninstalling = oclosure.0-dev
[WARNING] Command "rm -f" contains 1 spa= ce
The compilation of oclosure.0-dev failed in /Users/ashish/.opam/system= /build/oclosure.0-dev.

[ERROR] while installing oc= losure.0-dev
=3D [RUN] "configure --prefix /Users/ashish/.op= am/system"
=3D [CWD] "/Users/ashish/.opam/system/build/oclosure.0-dev"<= /div>
... lots more environment variables printed

<= div>However, manually cd'ing to=A0/Users/ashish/.opam/system/build/oclo= sure.0-dev, then running the configure, make, commands behaves differently.= The configure succeeds. The make runs for a while (but I did not let it ru= n to completion). Question is what is opam doing differently then running t= he commands manually? Is there some way to see the error messages when opam= install fails?

Also, note this failure happens on Mac OS X but the sam= e repo succeeds for us on CentOS and Ubuntu.

--e89a8fb1f7ee0a8efb04ce4e056a--