Conversation

Notices

1. Embed this notice
   Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Sunday, 19-May-2024 02:22:17 JST Ekaitz Zárraga 👹

   • Andrius Štikonas

   So yeah, @stikonas and myself bootstrapped GCC 4.6.4 for #RISCV (with C++ support)

   Read more:

   https://ekaitz.elenq.tech/bootstrapGcc14.html

   • Embed this notice
     Andrius Štikonas (stikonas@fosstodon.org)'s status on Sunday, 19-May-2024 02:22:09 JST Andrius Štikonas

     in reply to

     • Ludovic Courtès
     • Janneke

     @civodul @ekaitz_zarraga @janneke Yes, tweaking mes would have required far bigger changes: rewrite all I/O there to use FILE structures, wide character strings and probably other things too. Anyway, it's just another package, not that much more different from GMP, MPFR or MPC that we also added.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Sunday, 19-May-2024 02:22:11 JST Ekaitz Zárraga 👹

     in reply to

     • Ludovic Courtès
     • Andrius Štikonas
     • Janneke

     @janneke @civodul @stikonas Using Musl is a very good compromise, too.
     It's supereasy to read, and many of the problems we have fixed in meslibc we used musl as a reference so... Somehow meslibc is more similar to musl now. If we continue to do so, maybe it will become musl at some point hehe.

   • Embed this notice
     Ludovic Courtès (civodul@toot.aquilenet.fr)'s status on Sunday, 19-May-2024 02:22:11 JST Ludovic Courtès

     in reply to

     • Andrius Štikonas
     • Janneke

     @ekaitz_zarraga I see, thanks for explaining!

     I think it’s great that you found a solution that works. For Guix at least, we also need to look at the bigger picture and see how to best address it with a whole-system approach.

     To me that probably means tweaking Meslibc (which, of course, is easier said than done).

     @stikonas @janneke

   • Embed this notice
     Janneke (janneke@todon.nl)'s status on Sunday, 19-May-2024 02:22:14 JST Janneke

     in reply to

     • Ludovic Courtès
     • Andrius Štikonas

     @civodul @ekaitz_zarraga @stikonas in any case, it's always much easier to change or enhance a working solution than to get it working in the first place.

   • Embed this notice
     Janneke (janneke@todon.nl)'s status on Sunday, 19-May-2024 02:22:15 JST Janneke

     in reply to

     • Ludovic Courtès
     • Andrius Štikonas

     @civodul @ekaitz_zarraga @stikonas my idea was (is) to enhance mes lib c so that it can build gcc-4; but that's still in progress for x86, and riscv is "waiting" for that.

   • Embed this notice
     Ludovic Courtès (civodul@toot.aquilenet.fr)'s status on Sunday, 19-May-2024 02:22:16 JST Ludovic Courtès

     in reply to

     • Andrius Štikonas

     @ekaitz_zarraga @stikonas Yay, congrats!

     Maybe I missed an episode, but why bring another libc into the mix?

   • Embed this notice
     Andrius Štikonas (stikonas@fosstodon.org)'s status on Sunday, 19-May-2024 02:24:04 JST Andrius Štikonas

     in reply to

     • Ludovic Courtès
     • Janneke

     @janneke @ekaitz_zarraga @civodul Well, I guess the first point is similar to Xorg stuff. Xorg is also MIT but we do ship in in Guix. And both are GPL-compatible, so you can take a any improvements from musl and move to meslibc.

     Hurd is a more interesting point. For real baremetal bootstrap neither Hurd nor Linux kernels are good anyway, you need something far simpler. But for userspace only bootstrap (as in Guix) that's definitely a valid point.

   • Embed this notice
     Andrius Štikonas (stikonas@fosstodon.org)'s status on Sunday, 19-May-2024 02:24:04 JST Andrius Štikonas

     in reply to

     • Ludovic Courtès
     • Janneke

     @janneke @ekaitz_zarraga @civodul Porting musl to Hurd might not be too hard. For x86 baremetal (from BIOS) bootstrap Rick Masters ported musl to Fiwix kernel with just a few patches.

     That said I understand that you might still want to improve meslibc longer term even if it is harder.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Sunday, 19-May-2024 02:24:08 JST Ekaitz Zárraga 👹

     in reply to

     • Ludovic Courtès
     • Andrius Štikonas
     • Janneke

     @civodul @janneke As @stikonas says, musl is just another package.
     Why does it feel right to add TinyCC but we prefer to avoid Musl?
     In the same way it would be great to use MesCC to build GCC4.6.4 but that's not possible right now for two reasons: it would take forever to build and it needs many improvements in MesCC to make this possible.

     Same thing happens with MeslibC. MeslibC is just very problematic at this very moment.

   • Embed this notice
     Janneke (janneke@todon.nl)'s status on Sunday, 19-May-2024 02:24:08 JST Janneke

     in reply to

     • Ludovic Courtès
     • Andrius Štikonas

     @ekaitz_zarraga @civodul @stikonas musl's anti-GNU/GPL sentiment, but mainly the the Hurd.