Conversation

Notices

1. Embed this notice
   Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Tuesday, 12-Mar-2024 00:23:24 JST Ekaitz Zárraga 👹

   • clacke
   • Efraim Flashner

   @clacke @efraim It's not that difficult fix tbh it's a matter of taking a decision.
   We must define where the compilers need to search for their stuff.
   There are answers in the ML that have solutions for it but they've never been discussed for inclusion in guix...
   We need to improve on that.

   • Embed this notice
     Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Tuesday, 12-Mar-2024 00:21:33 JST Ekaitz Zárraga 👹

     I just want gcc cross compilation environments to work in #guix so I can do something cool with hardware and RP2040s...

   • Embed this notice
     Efraim Flashner (efraim@tooot.im)'s status on Tuesday, 12-Mar-2024 00:21:38 JST Efraim Flashner

     in reply to

     @ekaitz_zarraga
     I'm trying to compile the firmware for my pinetime and I've been failing for about a month so far.

   • Embed this notice
     Efraim Flashner (efraim@tooot.im)'s status on Tuesday, 12-Mar-2024 00:24:00 JST Efraim Flashner

     in reply to

     • clacke

     @ekaitz_zarraga @clacke
     I'm compiling for arm-none-eabi and i've been using a full (cross-gcc-toolchain "arm-none-eabi") but the {CROSS_,}C{PLUS,}_INCLUDE_PATH is causing trouble between the specialized toolchain and the regular packages. I haven't gone as far as explicitly setting the *_INCLUDE_PATHS but I'm actually leaning that direction now.