13:59 <kensan> Is mirage.io currently not responding or is the problem on my side?

14:00 <reynir> not just you

14:02 <jpdeplaix> +1

14:02 <jpdeplaix> cc hannes

14:15 <hannes> jpdeplaix: no need to cc me, I don't have any access on mirage.io. it's all in anil's hand

14:25 <jpdeplaix> he can't do it for now but will later. I'll post on the slack to keep track

14:47 <damjan> trying to install mirage I get this "The following actions failed ∗ install ocamlfind 1.7.3-1"

14:48 <hannes> damjan: which OS + OCaml version? did you run "eval `opam config env`" after opam switch xxxx?

14:48 <damjan> http://vpaste.net/JHRy0

14:48 <damjan> hannes: ocaml and opam are installed from distro packages - it's Archlinux

14:48 <hannes> damjan: or is it a "system" switch (i.e. OCaml installed by the OS, rather than via opam?) -- this seems to end up in troubles..

14:49 <damjan> it is

14:49 <damjan> .opam/config says "switch: "system"

14:49 <damjan> "

14:49 <hannes> damjan: could you "opam switch 4.05.0" to have a fresh compiler compiled by opam, and afterwards run "eval `opam config env`" and opam install mirage?

14:50 <damjan> btw, the packaged ocaml is "The OCaml toplevel, version 4.06.0"

14:50 <damjan> ok brb, downloading

14:50 <hannes> then 4.06.0 -- the xen backend atm is 4.04.2 and 4.05.0 only, the kvm + unix backends are happy with 4.06.0

14:51 <damjan> kvm is fine with me :)

14:51 <jpdeplaix> damjan: got it

14:51 <jpdeplaix> you need to install ocaml-compiler-libs

14:51 <jpdeplaix> it seems that some distributions installs it separately

14:51 <damjan> jpdeplaix: wait, so I run switch or not?

14:51 <damjan> aha

14:52 <jpdeplaix> no, just use the system switch it should work fine from now on

14:52 <jpdeplaix> (hopefully)

14:52 <hannes> jpdeplaix: oh, thanks for jumping in.. I'm not a GNU/Linux user ;p

14:53 <damjan> aha, it's an Arch package too

14:53 <hannes> and read quite some issues about broken system packages every now and then..

14:53 <jpdeplaix> I just had to ask David ^^"

14:53 <damjan> yey

14:53 <damjan> building

14:53 <jpdeplaix> good ! :)

14:55 <hannes> \o/

14:55 <jpdeplaix> I'll fix the opam package

14:56 <damjan> The following actions failed * install base v0.10.0 ∗ install ocaml-compiler-libs v0.10.0 ∗ install ocaml-migrate-parsetree 1.0.7

14:56 <jpdeplaix> crap

14:57 <jpdeplaix> do you have any more logs ?

14:57 <damjan> why does it try to install compiler-libs 0.10.0 when I installed extra/ocaml-compiler-libs 4.06.0-1 [installed]

14:57 <damjan> jpdeplaix: yes, just a sec

14:57 <damjan> http://vpaste.net/pK6Qi

14:59 <damjan> do I need to install something else from the Arch package? http://vpaste.net/TgvTI

14:59 <damjan> packages*

15:09 <jpdeplaix> oh....

15:09 <jpdeplaix> that might be a problem with the archlinux package

15:11 <jpdeplaix> yes it. I'll send an email to the maintainer :/

15:11 <jpdeplaix> it is*

15:24 <damjan> jpdeplaix: what exactly is the problem? I'm an ocaml newbie

15:26 <jpdeplaix> well, the ocaml-compiler-libs packages from archlinux only installs the bytecode version of the library but the compiler installs the both the bytecode version and the native one

15:26 <jpdeplaix> usually the two packages are installed together but for some reason archlinux decided to split them

15:27 <damjan> so the bug report would be "install native version of the package too"?

15:27 <damjan> I can do that :)

15:28 <jpdeplaix> some ocaml libraries need compiler-libs to be built and correctly detects that the compiler supports the native version and thus try to compile against the native version of the compiler-libs

15:28 <jpdeplaix> I've already sent an email to the maintainer, don't worry

15:32 <jpdeplaix> oh. Seems like there is already a bug report: https://bugs.archlinux.org/task/57200

15:46 <reynir> damjan: I'd recommend using a separate switch (not 'system') on Archlinux since it's a pain in the butt when pacman updates e.g. OCaml and all the opam packages break

15:46 <reynir> (I wonder if you can do 'opam switch reinstall system')

15:46 <damjan> ah :/

15:47 <damjan> opam switch 4.06.0

17:50 <damjan> # /home/damjan/.opam/4.06.0/build/solo5-kernel-ukvm.0.2.2-1/kernel/ukvm/solo5.o:/home/damjan/.opam/4.06.0/build/solo5-kernel-ukvm.0.2.2-1/kernel/ukvm/io.c:95: more undefined references to `__stack_chk_fail' follow

18:53 <hannes> damjan: sounds to me like some gcc option for stack safeguarding is enabled by default and needs to be explicitly disabled..

18:53 <damjan> oh, most probably

18:54 <dstolfa> hannes: or explicitly linked in if they want to use it

18:57 <hannes> dstolfa: well, so our OCaml runtime etc. is compiled without red zone etc. -- since we're happy in ring0 :D ... afaict (but not sure entirely since there's quite some delta in the solo5 repository compared to the latest release) the ukvm thing over there is part of the guest system...

18:58 <hannes> damjan: another option is to "opam pin add solo5-kernel-ukvm --dev" to instead use the current git master, which may have the issue already fixed

19:00 <damjan> seems to have worked