<rekado>I'm commenting the line for now; ultimately, I think our cross-gcc procedure needs to be a little more flexible.
<rekado>I'm building the firmware for the axoloti board.
<rekado>actually, the firmware itself has been built already, but audio patches require g++, so I'm stuck there.
<rekado>I already got sound out of the board (a short click indicating that the firmware was applied and the audio output was initialised), but to actually get it to play synth patches I need to compile them with cross-g++.
<rekado>civodul: there's a comment above the "--enable-languages=c", but I'm not sure it applies in my case. Will see.
<davexunit>man, I don't know if I can handle guix-help, too many people insisting that we are doing everything wrong.
<davexunit>first we had people suggesting we use Docker and use pre-build jars, and now there are suggestions that we should use sysvinit
<rekado>civodul: the comment is correct. When c++ is not disabled we eventually get this error when building the cross compiler: "checking for shl_load... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES."