search

ocaml-attic / mirari

Mirage Application Builder
6 stars 5 forks source link

Do we have to hardcode "4.01.0dev+mirage-xen"? #6

Closed djs55 closed 11 years ago

djs55 commented 11 years ago

This means that (eg) mirage-www fails to build on 4.00.1+mirage-xen with an error:

cd src && mirari configure www.conf --xen --no-install
Using specified config file www.conf
Generating ./main.ml.
Creating ./filesystem_static.ml.
+ Executing: opam config exec "mir-crunch -o ./filesystem_static.ml -name "static" ./../files" --switch=4.01.0dev+mirage-xen
### stderr ###
The current switch (4.01.0dev+mirage-xen) is an unknown compiler switch. Switching back to 4.00.1 ...
'opam config exec mir-crunch -o ./filesystem_static.ml -name static ./../files --switch=4.01.0dev+mirage-xen' failed.
Fatal error: exception opam: "execvp" failed on mir-crunch: No such file or directory
ERROR: The command "opam config exec \"mir-crunch -o ./filesystem_static.ml -name \"static\" ./../files\" --switch=4.01.0dev+mirage-xen" exited with code 1.
make: *** [src/dist/setup] Error 1

It also switched me back to 4.00.1 (from 4.00.1+mirage-xen) which confused me.

avsm commented 11 years ago

Perhaps putting something in the .conf file for this? That's where everything ese is.

vbmithr commented 11 years ago

No you don't, it supports arbitrary compiler specification in the conf file, or at least it was designed that way. I will have a look soon.