<miragebot>
mirage/master a7db161 Hannes Mehnert: link libgcc.a only on ARM, not on X86
<miragebot>
mirage/master c20db8f Hannes Mehnert: also move pkg-config call to EXTRA_LD_FLAGS
<miragebot>
mirage/master 21fc794 Hannes Mehnert: move additional ld flags into a Makefile variable...
miragebot has left #mirage [#mirage]
<hannes>
mato: I commented on the issue... my current plan is to go ahead and move mirage-entropy-xen to topkg which will ease the addition of mirage-entropy-solo5 (in the same repo, different package), avoiding code duplication.. today at IETF meeting, but will hopefully finish that tonight (and send a PR to solo5-opam repo)
mort___1 has joined #mirage
mort___ has quit [Ping timeout: 272 seconds]
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<mato>
hannes: Thanks. I just commented on the header file issue, unfortunately not looking good ...
<hannes>
yes, no worries... go ahead with gcc only support for now
<hannes>
(well, if you can include the type 1 headers now, although it is pointless, it would help me already (or if you have some branch for that))
<mato>
I don't -- was going to do it today but with the group 2 problem I don't want to do it now as it's a fair bit of work and the gain is not clear.
<mato>
Also, I don't want to break the current setup which works :-)
<hannes>
ack
<mato>
I will however test #63 (don't link libgcc.a) and merge if it all checks out.
<hannes>
as said, I'll move along with entropy (I've a PR to use topkg), and try to poke david about nocrypto changes..
<mato>
thanks. these things take time. I can start publishing most packages soon and possibly also submit the PR to the mirage frontend, the backend will just not work for any unikernel which depends on nocrypto/entropy without using the opam-solo5 remote...
<mato>
once that gets sorted then things should start working using just opam.ocaml.org
<hannes>
mato: ack. you'll first need to get mirage-solo5 (and their dependencies) in there
<mato>
hannes: indeed, enough to do there, so i'm not blocked by waiting on nocrypto
<hannes>
mato: exactly. and for nocrypto I already got a mirage-no-solo5 into opam-repo
<mato>
great
<hannes>
and in the end, we'll have to wait for mirage-3 to get it all out of the box... which likely will take some more time..
<mato>
ack.
insitu has joined #mirage
<hannes>
bbl
miragebot has joined #mirage
<miragebot>
[mirage] yomimono pushed 8 new commits to master: https://git.io/vKrIx