09:17 <adamsteen> Hey Mato

09:22 <mato> adamsteen: Hi Adam!

09:23 <mato> adamsteen: I've made some progress, with avsm's help have a working OPAM 2 install on OpenBSD 6.3

09:23 <adamsteen> i have testing OPAM 2 yet

09:23 <mato> adamsteen: Which needs to be built from source; I'll add the steps to our OpenBSD issue

09:23 <adamsteen> havent sorry

09:24 <mato> I could not get OPAM 1 to work due to the external solver not being available and no aspcud

09:24 <mato> So just gave up on that

09:24 <adamsteen> Arrh yes! I had to build all that from scratch too

09:24 <mato> Am now trying to figure out the pkgconf/pkg-config problem

09:24 <mato> OPAM 2 install is actually pretty straightforward if you know the steps to use

09:24 <adamsteen> now that would be nice!

09:24 <adamsteen> I will be around, if you need anything

09:25 <mato> AFAICT the problem is that /usr/bin/pkg-config does not support ${pcfiledir}

09:26 <mato> In theory that could be fixed by generating all the Mirage .pc files with a fixed ${prefix} at install time, but that's quite a pain

09:27 <adamsteen> its it possible to make the pkg-config a variable? and default it to pkg-config?

09:27 <mato> That would be the same amount of effort

09:28 <adamsteen> oh

09:28 <mato> I think the easiest option right now is to try and detect the situation if running on OpenBSD (at the time solo5-kernel-ukvm is built) and complain to the user if they don't have the "right" pkg-config in $PATH

09:29 <mato> it's a hack, but I can't think of anything easier right now

09:30 <mato> long term the proper fix would be to stop using pkg-config entirely and use OPAM per-package variables to pass the values around, but that would make us depend on OPAM 2

09:31 <adamsteen> It makes sense to me and is very easy to setup

09:32 <mato> anyway, let me set $PATH and actually test the rest of your changes to see if everything works

09:32 <adamsteen> i will be in and out over the next hour then i probably won't be back till about 12:30pm utc ( or 8:30am in Perth Australia)

09:34 <adamsteen> also note anything with gmp-freestanding will fail, i have fixes up until nocrypto, nothing worth a pr yet tho

09:34 <mato> sure

09:35 <mato> i have about an hour as well...

09:35 <mato> adamsteen: will you be around tomorrow morning CET?

09:37 <adamsteen> before 9am maybe

09:37 <adamsteen> its 5:30pm here

09:38 <adamsteen> I have a work function from 4pm here ( or 9am CET)

09:38 <mato> ok, thanks, I might just merge the existing PRs as-is, then sort out the pkgconf problem in a followup. Will decide this afternoon.

09:41 <adamsteen> I will still be here for the next 40mins or so

09:42 <adamsteen> i will thinking about the pkgconf problem further and see what I can come up with

09:44 <hannes> (adamsteen btw your nocrypto patch breaks installation on my system as well, it also needs to be different from the mirage-solo5 approach since nocrypto is also used with unix (and there we want to install a shared library, and only have the cross-compiled c sources for solo5 come without a shared library)

09:44 <mato> Well, once opam depext is fixed on openbsd, what we could do is -- if we detect the situation on OpenBSD we install the symlink ourselves in the opam install script for solo5-kernel-ukvm, into the per-OPAM bin directory

09:44 <mato> (and print a prominent warning)

09:46 <adamsteen> i think opam depext was merged 25mins ago, just got an email

09:50 <mato> yes, altgr just told me, but it needs testing before releasing a new version

09:50 <mato> however, i have a different problem: https://0bin.net/paste/6tOBRQeO3FYHbFDG#Bx23Lj6Cqe11zoWnDypkN0f720D6znRZ1MIudjo6csp

09:51 <mato> adamsteen: have you seen that before? note that the data seg size (and heap) looks completely wrong

09:51 <mato> and the rip is bogus

09:51 <mato> this is from the mirage-skeleton tutorial/hello

09:51 <adamsteen> A quick question are you running current or 6.3?

09:51 <mato> 6.3

09:52 <hannes> (adamsteen: i suspect the nocrypto issue needs fixing in ocb-stubblr... all these build systems are painful :/)

09:52 <adamsteen> hmm, i am current current, i will need to set something up to verify whats going

09:52 <adamsteen> (hannes: thank you, i think I need to park that for a little while anyways)

09:52 <adamsteen> i saw that once for a couple of days in current

09:53 <adamsteen> but it went away on my next snapshot update

09:53 <hannes> (adamsteen: i may look into it later today)

09:53 <adamsteen> its something happening between the pledge or change root

09:54 <adamsteen> ie the security specific code

09:54 <adamsteen> if you would like i can just remove that for now and open a new pr to get it back in, when i have verified it on 6.3 and current

09:55 <mato> well, TBH, I'd kind of prefer to deal with de-privileging separately

09:55 <mato> I realise that on OpenBSD it's supposed to be "baked in", but I think we should get things working first :)

09:55 <adamsteen> https://github.com/adamsteen/solo5/blob/openbsd/ukvm/ukvm_hv_openbsd_x86_64.c#L168-L190

09:56 <adamsteen> ok give me a couple of minutes

09:56 <mato> adamsteen: should i try and remove it locally first to see if it helps at all?

09:56 <mato> adamsteen: or just push to a separate branch that I can "opam pin" to (not to the PR yet)

09:56 <adamsteen> ok will do

09:57 <mato> thx

09:57 <mato> though I suspect the problem is elsewhere since the C tests work...

10:01 <adamsteen> https://github.com/adamsteen/solo5/tree/temp

10:03 <adamsteen> i have only seen the issue for one working session, and then I updated the snapshot as i need a new package and it has went away

10:04 <mato> adamsteen: nope, no change... same result

10:05 <adamsteen> mato: oh, i apologise, i will need to get 6.3 up and running and see what the issue is

10:05 <mato> and if I run the C "test_hello" with the same ukvm binary (the one that mirage build produced), it works fine

10:05 <mato> adamsteen: no need to apologise; these things are tricky!

10:06 <mato> adamsteen: for reference, this is with the Solo5/opam-solo5 repo, and the following pins:

10:06 <mato> ocaml-freestanding.dev~solo5 git git+file:///home/build/ocaml-freestanding#openbsd

10:06 <mato> solo5-kernel-ukvm.dev~solo5 git git://github.com/adamsteen/solo5#temp

10:07 <mato> (the ocaml-freestanding is your openbsd branch)

10:08 <adamsteen> cheers, i will have a look into it when i can

10:08 <adamsteen> brb gotta get the dog some food

10:11 <mato> no worries

10:15 <adamsteen> i think thats my cue to go

10:16 <adamsteen> i will be interested in your opam2 information

10:17 <adamsteen> and i will look into whats going on with 6.3 vs Current and mirage hello tutorial

10:17 <adamsteen> glad i could get on here for a bit

10:25 <mato> adamsteen: cool, thanks for dropping in

10:26 <mato> adamsteen: if things look mergeable tomorrow AM my time then I'll click some buttons

10:26 <mato> adamsteen: otherwise after I get back from sailing (14th)

10:33 <adamsteen> mato: good night/day, i suspect it will be when you get back, i am thinking its a OpemBSD kernel vmm thing, which would mean 6.4 would be the next stable that would be work

10:34 <adamsteen> hannes: good night/day, that would be cool if you got somewhere with nocrypto, but i now have more import things to sort, mirageos on OpenBSD 6.3

10:34 <adamsteen> caio all