Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-21 Thread Sylvain Le Gall
Le mer. 20 mai 2015 à 12:02, Martin Lucina a écrit : > On Tuesday, 19.05.2015 at 15:58, Martin Lucina wrote: > > > >E: Failure("Expected built file '_build/src/unix/dlllwt-unix_stubs.so' > > > >doesn't exist.") > > > > > > > >This is expected; the rumprun toolchain does not support dynamic > > >

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-20 Thread Martin Lucina
On Wednesday, 20.05.2015 at 12:02, Martin Lucina wrote: > Getting further through the list of Mirage dependencies, trying to get > sexplib building for rumprun hits another different problem with OASIS: *facepalm* Ok, sorry, this was caused by a two-character typo: ["ocaml" "setup.ml" "-configure

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-20 Thread Martin Lucina
On Tuesday, 19.05.2015 at 15:58, Martin Lucina wrote: > > >E: Failure("Expected built file '_build/src/unix/dlllwt-unix_stubs.so' > > >doesn't exist.") > > > > > >This is expected; the rumprun toolchain does not support dynamic > > >linking > > >and I have configured the ocaml-rumprun compiler with

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Peter Zotov
On 2015-05-19 17:39, Martin Lucina wrote: On Tuesday, 19.05.2015 at 17:15, Peter Zotov wrote: On 2015-05-19 16:58, Martin Lucina wrote: >This begs the question, why did you use the approach of building the >cross-compiler as a normal OPAM package, rather than as a compiler >package? Because the

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Thomas Gazagnaire
> And, as I just found out now, it's not just the native packages, it's *all* > packages that need to be rebuilt. So, for Mirage I'd have to produce > -rumprun variants of all its dependent packages, right? This would include > teaching the "mirage configure" script about them. We already partly d

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Martin Lucina
On Tuesday, 19.05.2015 at 16:12, Martin Lucina wrote: > In theory PR#6266 > (https://github.com/ocaml/ocaml/commit/c1e26ad14aec62cefe3d5fb24cf8702caa39db2b) > might fix these options to let me run OCaml configure directly against the > rumprun cross compiler but I've not tried yet. See also htt

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Martin Lucina
On Tuesday, 19.05.2015 at 17:15, Peter Zotov wrote: > On 2015-05-19 16:58, Martin Lucina wrote: > >This begs the question, why did you use the approach of building the > >cross-compiler as a normal OPAM package, rather than as a compiler > >package? > > Because the cross-compiler needs a normal co

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Peter Zotov
On 2015-05-19 16:58, Martin Lucina wrote: This begs the question, why did you use the approach of building the cross-compiler as a normal OPAM package, rather than as a compiler package? Because the cross-compiler needs a normal compiler (and its runtime) to build and execute. Because many pac

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Martin Lucina
Hi Thomas, On Tuesday, 19.05.2015 at 12:49, Thomas Gazagnaire wrote: > Lwt's discover.ml is unfortunately known to be very ad hoc and often breaks > so I am not very surprised. Usually patches to fix it sent upstream are > kindly accepted (until someone be brave enough to completely rewrite that

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Martin Lucina
On Tuesday, 19.05.2015 at 14:09, Peter Zotov wrote: > >What can be done to fix the above? Should I be using a host > >compiler built > >and installed by OPAM rather than the system compiler > >(4.02.1-1ppa3~precise > >on Debian wheezy). [I'll try this and see if it helps...] > > No. This is an iss

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Peter Zotov
On 2015-05-19 11:50, Martin Lucina wrote: Rumprun provides a unikernel stack with a POSIXy (NetBSD-HEAD) userspace and can run on Xen, QEMU/KVM, bare metal and POSIX userspace. The resulting Mirage + rumprun unikernel will thus be able to run on all of the platforms rumprun supports. Nice!

Re: [MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Thomas Gazagnaire
Hi Martin, > My work in progress OPAM repository is here: > > https://github.com/mato/opam-rumprun > > This is enough to get an OCaml "Hello, World" running on rumprun, and I've > also tested that the Unix package works as expected. So far so good. That's really great! Looking forward to use Mi

[MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Martin Lucina
[Re-sending with correct opam-devel address] Hi all, I'm working on getting OCaml and Mirage OS running on top of the rumprun unikernel stack[1]. Rumprun provides a unikernel stack with a POSIXy (NetBSD-HEAD) userspace and can run on Xen, QEMU/KVM, bare metal and POSIX userspace. The resulting

[MirageOS-devel] Cross-compiling OCaml, Mirage OS for rumprun, OPAM integration

2015-05-19 Thread Martin Lucina
Hi all, I'm working on getting OCaml and Mirage OS running on top of the rumprun unikernel stack[1]. Rumprun provides a unikernel stack with a POSIXy (NetBSD-HEAD) userspace and can run on Xen, QEMU/KVM, bare metal and POSIX userspace. The resulting Mirage + rumprun unikernel will thus be able t