Re: [MirageOS-devel] cubieboard2/truck users and opam 1.2

[Luke Dunstan <lukedunstan81@xxxxxxxxx>]

A week ago I started using this binary:Âhttps://github.com/ocaml/opam/releases/download/1.2.0/opam-1.2.0-armv7l-Linux

I just renamed it to "opam" and put it in a directory that is earlier in PATH than /usr/bin. It seems to work fine, but is there any reason why this might cause problems?

Luke

On 3 November 2014 06:50, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:

On 2 Nov 2014, at 22:46, David Scott <scott.dj@xxxxxxxxx> wrote:

On Sun, Nov 2, 2014 at 8:57 PM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:

For Cubieboard2 users, the Launchpad OPAM builds do end up with armhf images, but you can't use the PPA commands since the distribution template of our Cubie image is 'Linaro' instead of 'Ubuntu' (not sure why we can't just switch to a pure Ubuntu or Debian image).

Anyway, these four simple commands will get you OPAM 1.2.0 without having to do a source compilation, as root:

echo "deb http://ppa.launchpad.net/avsm/ocaml41+opam12/ubuntu trusty main"Â > /etc/apt/sources.list.d/ppa-opam.list
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5B2D0C5561707B09
apt-get update
apt-get upgrade

This worked nicely for me. I was able to (from memory, hope I've not typo'ed it)

opam init

eval `opam config env`

opam remote add mirage-dev git://github.com/mirage/mirage-dev

opam install mirage

git clone git://github.com/mirage/mirage-skeleton

cd mirage-skeleton

MODE=xen make configure

MODE=xen make build

and all the examples built ok.

Coincidentally, the same asÂhttps://github.com/mirage/is-mirage-broken/blob/master/scripts/build_mirageÂ!

-anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel