Conversation

Notices

1. Embed this notice
   byte :ms_robot_headpats: (byte@awawa.club)'s status on Saturday, 24-May-2025 00:08:01 JST byte :ms_robot_headpats:
   cross-compilation was a mistake
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Saturday, 24-May-2025 00:07:59 JST anna

     in reply to
     @byte non-cross-compilable software is usually the mistake
     
     * navi screams at glib again
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 24-May-2025 00:15:22 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • anna
     @navi @byte Not sure for glib (as I strongly avoid it) but usually it's just the buildsystem being ass.
     
     Meanwhile for good buildsystems it's just setting which toolchain you want, not much more complex than choosing gcc+binutils or clang.
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Saturday, 24-May-2025 00:17:38 JST anna

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @byte glib uses meson, the problem isn't the build system
     
     glib wants to compile *and* run code during build time to do it's "introspection" bs, meaning to cross-compile glib you *need* to setup qemu as an exe wrapper
     
     and on top of that, after i built aarch64 qemu just for glib, it still goes and gets confused trying to build and load x86_64 cpython modules
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 24-May-2025 00:23:03 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • anna
     @navi @byte Well by buildsystem I do include code in files like Makefile / configure.ac / meson.build / … which you can either fix (done on a regular basis) or toss out and get the same software out (oasis linux does that, and I've seen that done quite few times by annoyed packagers as well).
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 24-May-2025 00:38:11 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • anna
     @navi @byte *looks into how Buildroot does it*
     Yup qemu… ugly.
     
     And course glib also doesn't self-bootstraps gobject-introspection so there's a libglib-bootstrap stage without introspection, well done…
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Saturday, 24-May-2025 00:38:12 JST anna

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @byte well yea but here the problem is inherent to glib's design, their code works only by running specifically target code during the build, which is a stupid thing to do
   • Embed this notice
     [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic: (novenary@akko.wtf)'s status on Saturday, 24-May-2025 01:08:52 JST [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic:

     in reply to
     @navi @byte @lanodan that's still a misconfigured build system, if it needs to run code at build time it should build that for the build machine, not the host
     and if that somehow causes problems, at this point their shit is just broken 🤡
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 24-May-2025 01:26:19 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • anna
     • [GRLC] (⁠^⁠.⁠_⁠.⁠^⁠)⁠ﾉ :neocat_flag_sapphic:
     @novenary @byte @navi I'd probably point towards broken, it *is* glib after all, I've banned it on servers because it tends to abort on errors.