-
Notifications
You must be signed in to change notification settings - Fork 36
ERROR while installing mirage-xen.1.1.1 on ARM #45
Comments
this is fixed in the next rebuild (which is happening right now) you are using an out of date opam repository so: cd opam-repository
|
sorry, what do you meet by opam-repository, clone https://github.com/mirage/xen or ~/.opam/packages/mirage or something else? |
for ref, i tried:
This still fails as "Requested 'libminios-xen >= 0.5' but version of mini-os is 0.2". OPAM still doesn't see mirage-xen-minios packages after version 0.4.1 so I tried redoing the process for mirage-xen-minios and mirage-profile.0.1 its now failing at the make with
Is there a way to make use of the xen-arm-builder fix without starting all over again ? |
mirage-xen-minios.0.6.0 is in the public OPAM repository, so it should be found: http://opam.ocaml.org/packages/mirage-xen-minios/mirage-xen-minios.0.6.0/ What does |
sorry i've dd'ed over the sd card now so i can't test it further but it said version number doesn't exist. I tried opam update many time but I just would not acknowledge that there was versions after 4.0.1 |
"opam update" doesn't work with the manually cloned opam repository in ~/opam-repository so you probably have an old version from when the image was generated. You should be able to update by running "git pull" in ~/opam-repository. If it doesn't work you could try to delete .opam and then run "opam init" again, but you have to reinstall/recompile all packages. |
It's in the git/opam-repository subdir |
fixed, needed to start fresh again and do
|
[sorry if this is the wrong issue tracker, it's ARM related so I've put it here]
after using xen-arm-builder and following the instructions at http://openmirage.org/wiki/hello-world,
opam fails to install mirage-xen.1.1.1 with the following error on cubieboard2:
gcc version
the error from opam after make depend
This compiling on the cubieboard2 (also the target) and not cross-compiling. The unknown options are relating to x86
The text was updated successfully, but these errors were encountered: