<reepca>Question... why does our clone procedure pass a null pointer as the child stack? How does that work?
<reepca>never mind, saw the bit about that tucked away in the man page
<efraim>I'm glad you figured that out because I had no clue and that just sounded strange
<catonano>some time ago I posted here a linkk to a tweet pointing to a talk by some illustrious clojurer about why it's important to have a single language in the whole stack. I can't remember it. Can anyone here gently point me back to it ?
<efraim>it turns out porting ccl to aarch64 isn't quite as trivial as copying platform-linuxarm.h to platform-linuxarm64.h and changing "32" to "64" in the new header file
<reepca>civodul: I finally pushed my local changes. I've run into a bit of a brick wall in trying to figure out what's going wrong. The guile builder for the bootstrap make is failing in a bizarre way, though it's more accurate to say the bootstrap guile itself is failing in a bizarre way. I asked a bit about it in #guile. Some low-level part of the bootstrap guile produces some sort of error, but the output says nothing about what kind of
<reepca>error, and attempting to invoke the bootstrap guile interactively from within the build environment causes it to display the copyright notice and immediately exit (exit code 0, though). Additionally, --no-auto-compile is ignored, but GUILE_AUTO_COMPILE=0 is honored.
<reepca>The issue only happens in the build environment. Aside from diving straight into guile's source to try to figure out what a "apply-smob/1" is and why it might fail, the only way I can think of continuing debugging is to slowly comment out isolation mechanisms and see when it starts working.
<quigonjinn>using 'guix system vm-image config.scm', I'm getting the error:"Could not access KVM kernel module: Permission denied, failed to initialize KVM: Permission denied". Any idea what the issue may be?
<civodul>quigonjinn: make sure /dev/kvm is read/write for your user
<quigonjinn>civodul: yes it is, my user is in the group dialout. I get the same error, running the command as root.
<quigonjinn>I can also run qemu with the --enable-kvm flag, though I don't know if that should be indicative or not
<reepca>civodul: description sent. Hopefully it's not too rambly, it's 5:00 in the morning over here
<civodul>reepca: indeed, for a minute i was wondering if you had changed time zones or something :-)
<nckx>solene: Yeah. Try the non-ISO .img (now available in delicious xz flavour!). If that doesn't work, and you can't fiddle with boot options to get it to, you'll have to talk to someone with more of a clue about UEFI than me.