IRC channel logs
2013-10-15.log
back to list of logs
<davexunit>could anyone help me with a pulseaudio issue? <mark_weaver>davexunit: in guix, builds run in a chroot and a private namespace (e.g. without networking, and with its own private set of process IDs, etc). maybe that's breaking shm_open somehow. <davexunit>I guess I'm curious as to how someone got this package in if the tests fail? <mark_weaver>but maybe some other things have been upgraded since then, and now it doesn't pass anymore.. or perhaps some impurities leaked into the build process, e.g. having to do with your kernel configuration or something. <mark_weaver>davexunit: can you send a bug report to bug-guix@gnu.org? <davexunit>I have an SDL package that is building, minus the pulse support. <davexunit>though I guess pulseaudio is an optional dependency? <mark_weaver>I'm juggling a 2.5-year-old at the moment, so my ability to read and write here are sporadic at best.. <gzg>mark_weaver: Overhand, or under? <bavier>davexunit: I can reproduce your shm_open error <bavier>There's a message later that seems related: "Failed to read /dev/shm/: No such file or directory" <bavier>maybe /dev/shm isn't accessible in guix's build jail <Steap>Did one of the latest commits trigger a massive rebuild of all packages ? <gzg>mark_weaver: Overhand, or under? <gzg>Woah, that was weird a weird hand twitch... <gzg>I somehow alt-p and entered in like half-a second... :^I <gzg>What I meant to ask, was what is considered a "guile development package"? I'm building my guile-xcb expression and I have guile-2.0 as an input -- but I'm getting "configure: checking for guile 2.2 configure: error: No Guile development packages were found.". <gzg>Oh wow didn't notice ... the config file is looking for a future version of guile. :^I <jxself>The config file is *from* the future, maybe? <jxself>It would explain a great many things. <gzg>Well, the latest git pull builds on my local machine -- the stable release doesn't on either. :^/ <mark_weaver>gzg: yeah, the guile-xcb tarball has several problems. you'd best try the latest from git. <mark_weaver>the problem with it looking for guile 2.2 is fixed in git. <gzg>mark_weaver: Very excited about the tech though and eventually possibly a wayland compositor and based toolkit may arise... :^) *gzg will probably just wait till December and if v2 of both aren't released, I'll just end up bugging mwitmer about it. :^) <gzg>mark_weaver: Yeah, I actually have -- that with guile-sdl (assuming they ever go to the 2.x branch), I'm looking very much forward to the way the tech on this side is advancing. <gzg>I was thinking of having my go at a tabletop interface with guile-figl and guile-sdl at some point. :^) <civodul>i restarted the queue-runner on hydra, but now another problem <a_e>What is the problem? <civodul>it's ridiculous: we install pretty much everything by hand on that machine <civodul>while we're working on a package manager <civodul>what's the English for that French saying? ;-) <a_e>Time to package hydra for guix, then. <civodul>but yeah, sounds like we'll have to do it <a_e>It is nice to see hydra back! <a_e>Probably I can go to bed with a good conscience - hydra will need more than a night to catch up. <zacts>I didn't realize that saying hello was so funny. :p <civodul>aah, it's the quote above that made me smile *zacts has to re-checkout guix master branch <zacts>I completely ruined my current branch somehow <civodul>gzg: did your post ever make it to bug-guix?