Re: Mirage Installation

[Anil Madhavapeddy <avsm2@xxxxxxxxxxxx>]

Dimos,

You're on the right track.  There was a bug a while back that would cause mirage-platform to install a script into /usr/local (the `mir-run` script).  I fixed that, and current opam should work.

However, there's a small quirk to be aware of.  The opam package manager remotes pointing to git:// urls might not be refreshed unless you do:

$ opam pin mirage-platform git://github.com/mirage/mirage-platform

$ opam update

$ opam upgrade

Do you want to try this and let me know if the error still persists?

cheers

Anil

On 29 Oct 2012, at 14:54, Dimosthenis Pediaditakis <dimosthenis.pediaditakis@xxxxxxxxxxxx> wrote:

Hi everyone,
I am new at the board, so excuse me if I ask trivial questions.

I installed Mirage using opam following the instructions found at
http://www.openmirage.org/wiki/install

My system's details are:
  Ubuntu 12.04.1 LTS
  3.2.0-32-generic 64bit
  The Objective Caml toplevel, version 3.12.1
  opam version 0.7.7
  (haven't installed Xen yet)

I do not want to install bins/libs under the default Linux path ( usr/{lib/bin} ) because I do not want to grant root privileges to the installers.

As a point of start I aim to run the mirage wiki website locally via the www-mirage package, through Unix binaries ( compiler 3.12.1+mirage-unix-direct ).

However, when I run "opam --verbose install mirage-www" without sudo, the installation fails while trying to install mir-run at "/usr/local/bin/mir-run".
I've seen that the default PREFIX in most mirage-related Makefiles is /usr/local (requiring root privileges).

In order to fix that issue, I export a custom prefix path before I proceed with the installation (e.g. export PREFIX=/data/bin).

Have I mis-configured Mirage during installation or the path /usr/local is the default hard-coded installation path for certain packages?

Regards,
Dimos