<zacts>mark_weaver: sorry, I've been slacking a bit due to some school stuff, and I've been busy out and about. <zacts>I'll look at it tomorrow, I have an exam tonight in a couple of hours. <zacts>I know zRecursive is wanting this soon also, and a few other people. <zacts>I'm just getting so tired of working with shars and FreeBSD ports, so I'm kind of procrastinating a bit too. <zacts>I really want to get started with guix <zacts>so will guix 1.0 be a full minimal distro? <zacts>and are the version numbers reflecting core changes, imported packages, or both? <mark_weaver>we're definitely aiming for being a self-contained distro, but I'm not sure how that will correspond to the version numbers. <mark_weaver>well, I think for now we're just trying to put out a release every 3 months or so. lots of changes and improvements happening. ***fangism1 is now known as fangism-ctrl-Z
<wingo>(pk 'ohai) is my favorite debugging device <sjoerd`>anyone else having problems with compiling eval.scm from commit af11242268c22fb80a102e66f142e0073f7889cc? <sjoerd`>lt-guile keeps hanging using > 60% CPU but no disk changes to the temporary go file <lloda>are you using an updated libgc / bdwgc? (7.4 I guess?) that's what fixed it for me. <sjoerd`>Right, I have a look at it. Might it be the case that I use multiple cores now? <sjoerd`>Just checked it, but yes, it's 7.4.0 <lloda>hm. I don't know what the ultimate source of the error is. It works for me with bdwgc-master. <wingo>sjoerd`: either update bdwgc from git, or build with GC_MARKERS=1 in the environment <sjoerd`>What is changed with GC_MARKERS and/or the updated bdwgc? <wingo>GC_MARKERS=1 disables parallel marking, and bdwgc 7.4.0 has a parallel marking bug that leads it to an infinite loop ***fangism-ctrl-Z is now known as fangism1