<rekado_>Sleep_Walker: the icedtea builds always took a little more than an hour on my machine. And the tests took much longer than that :) It's annoying when you get something wrong somewhere at the end.
<taylanub>davexunit: any error message or so? I don't know of a regression; just dlopen() calls that were never patched (so they never worked, probably .. unless if you're using guix on another system maybe)
<davexunit>I can't find anything yet. all I know is that an SDL call fails.
<iyzsong>I don't think the patch for mesa will get SDL/GL work, SDL can't find GL now >.<, I will fix it next day, if no one beat me.
<taylanub>by the way I thought ccache would not affect reproducability, or anything; I thought it intends to be 100% transparent, not changing compiler output in any way. of course, there is bug potential.
<davexunit>iyzsong: I can't find anything that shows that SDL can't find GL
<davexunit>the build looks good when glu is added as an input, and strace doesn't show anything alarming to me.
<taylanub>davexunit: any dlopen calls in the trace? any dangling .so references in ldd output for libsdl or w/e?
<davexunit>taylanub: how do I tell if a .so reference is dangling?
<taylanub>if the ldd output says "=> (not found)" or so for an .so, or points to a path that isn't /gnu/store/...
<taylanub>maximally generally, I wrote this dirty script to find all dangling .so references in one's /gnu/store, but it takes very long: http://sprunge.us/JEjD