From: Ashish Agarwal <agarwal1975@gmail.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] opam install seems not to run build command
Date: Mon, 12 Nov 2012 11:58:00 -0500 [thread overview]
Message-ID: <CAMu2m2+f5yv4JBSA8ezrKhmCo0PYHB8DoLhDWq=mk0PguLH2Yg@mail.gmail.com> (raw)
In-Reply-To: <87151241-0EF6-4BAE-A5CB-B0A1353895ED@recoil.org>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Thanks. Seems to be working.
On Mon, Nov 12, 2012 at 10:59 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 12 Nov 2012, at 15:32, Ashish Agarwal <agarwal1975@gmail.com> wrote:
>
> > 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
>
> This needs to be "./configure", or it'll fail if your PATH doesn't include
> the current directory. With this change, installation from Sebastien's
> remote works on my Mac.
>
> > make
> > make install
> > Uninstalling oclosure.0-dev
> > [WARNING] Command "rm -f" contains 1 space
>
> You should also change the ["rm -f"...] in the uninstall to ["rm" "-f"
> ...] to placate the execve(2) gods.
>
> -anil
[-- Attachment #2: Type: text/html, Size: 1710 bytes --]
prev parent reply other threads:[~2012-11-12 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 15:32 Ashish Agarwal
2012-11-12 15:59 ` Anil Madhavapeddy
2012-11-12 16:58 ` Ashish Agarwal [this message]
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+f5yv4JBSA8ezrKhmCo0PYHB8DoLhDWq=mk0PguLH2Yg@mail.gmail.com' \
--to=agarwal1975@gmail.com \
--cc=anil@recoil.org \
--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).