From: Ashish Agarwal <agarwal1975@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] opam install seems not to run build command
Date: Mon, 12 Nov 2012 10:32:53 -0500 [thread overview]
Message-ID: <CAMu2m2+qMUCyECGz961XYXc93wAJWsRK-roQrLG=OaHVMcUU0w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1842 bytes --]
next reply other threads:[~2012-11-12 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 15:32 Ashish Agarwal [this message]
2012-11-12 15:59 ` Anil Madhavapeddy
2012-11-12 16:58 ` Ashish Agarwal
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='CAMu2m2+qMUCyECGz961XYXc93wAJWsRK-roQrLG=OaHVMcUU0w@mail.gmail.com' \
--to=agarwal1975@gmail.com \
--cc=caml-list@inria.fr \
/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).