Hi All As some of you know I have been working to get MirageOS/Solo5 working on OpenBSD.
As of Friday of last week, I though i had at least achieved this, but after running an end to end test with released version the of Mirage-Skeleton Hello World Tutorial, I now find this causes as " mprotect W^X violation" on OpenBSD. I know Solo5 does not issue any mprotect requests with WRITE and EXEC permissions, but something in MirageOS does. I have be testing building the Hello World example for a while now without any problems of this nature, i am not sure where to start look at what changed. I can permit W^X memory on OpenBSD with a change to the Solo5 configure script and a file system setting, but this has now missed the boat for this release and would prefer not to do this. Any tips on where i should look? For anyone using OpenBSD wanting to test things you can follow the steps needed to get a working Solo5 + OPAM 2 installation on a fresh OpenBSD 6.3 install at https://github.com/Solo5/solo5/issues/206#issuecomment-386415256. I would run "opam init -a --compiler=4.06.1" to get the correct compiler version straight up. And a big thanks for Mato, Hannes and the rest of the Solo5 team in helping me get things going. Cheers Adam ps Should i post this on the MirageOS mailings instead?
