<rain1>ill see if there's a package that seems like it might ehlp
<marusich>One thing I found kind of useful is to compare your package definition with the package definition of a similar package already in Guix
<marusich>If you're lucky, it might be that one of the dependencies they used will pop out at you and you'll go, "Aha, I should have used that!"
<marusich>In the process of trying to package anthy and ibus-anthy for Guix, I've discovered that emacs has built-in Japanese language input support out of the box which just works. My mind has been blown. Emacs is so good!
<mark_weaver>it might require someone to dive head first into the build system and makefiles
<mark_weaver>GNU make has some debugging aids which probably produce massive quantities of output for a project like GCC, but that output could perhaps be searched for strings, e.g. makefile variables of interest
<mark_weaver>ACTION is relieved to discover that the audio-playing problems introduced since he last updated his Yeeloong system were not due to toolchain or C library, but due to the libao 1.1 -> 2.0 update.
<mark_weaver>oh, I got mixed up. there was never any update to 2.0. the 1.1 -> 1.2 update is what broke audio playback on the Yeeloong.
<davexunit>mark_weaver: yeah I need to look further. I dug as deep as I knew how to last time I looked at it.
<davexunit>the problem is as phant0mas described. everything builds successfully, avr-libc seems perfect, but avr-gcc is missing many libraries for almost every AVR chip.
<mark_weaver>davexunit: the substitutions done in the 'pre-configure' phase of the gcc-4.7 package (which is inherited by most other gcc variants) are fairly crude and approximate. it might be that they are causing problems in this case.
<davexunit>mark_weaver: that's where I left off. making heads or tails of that code proved tricky.
<mark_weaver>davexunit: the 'post-configure' phase might also be causing problems, dunno.
<mark_weaver>davexunit: the 'post-configure' phase is not essential, it is only to avoid retaining unneeded references, so you could try removing it for the avr gcc
<davexunit>mark_weaver: I'll just have to take another deep dive and hopefully I'll spot something that I didn't notice the last time around.
<lfam>That 10 second timeout is giving me 504. Probably best not to add to the load :)
<lfam>Okay, it loaded. Thanks for telling me how to catch my own fish.
<mark_weaver>in practice, there tend to be many spurious failures, often due to TCP connections being reset (probably by some pain in the ass firewall in between), which hydra interprets as real failures. so those things need to be restarted
<mark_weaver>I'm looking forward to the day when we have better software running on hyudra
<ng0>bad news. with my current traffic consumption, at least with one other project, it is hard to find an isp I could go to other than the one I am at now, so getting a guix mirror will happen when I can move my VMs to the first dedicated server with them.. which is anywhere from now to not specified point in the future.
<ng0>at that point it will possible not a mirror but a build machine if I can afford it.
<ng0>also, does someone know how I accidentally got an unremoveable mark stylized as "*" on a message in Gnus and how to remove it?
<mark_weaver>ng0: that means the message is "cached". you probably typed "*". to remove it, type M-*
<mark_weaver>see section 3.13 (Persistent Articles) of the Gnus manual
<ng0>that's harder to type than i thought with this keyboard
<mark_weaver>well, you need the shift key to get *, so on my US keyboard it's M-S-8
<ng0>i tried M * and it doesn't go away, but i'll try again
<mark_weaver>M * is different. do you know the emacs way of describing key combinations?
<mark_weaver>M-* means hold down the Meta key (often labelled "Alt") while typing *
<mark_weaver>so, on a US or UK keyboard, that means to hold down both Meta and Shift while pressing 8
<mik_>mark_weaver: my display size isn't getting picked up correctly. The configuration file that gets built looks correct, but I seem to be doing something wrong as every time I reboot the display size isn't correct