10 comments
@ekaitz_zarraga @civodul Indeed. You can go back to glibc after the next GCC is built. GCC 4.6.4 should be able to build anything from GCC 7.5 to GCC 10 (though right now I've only tried 7.5). And that should be good enough to build glibc. @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. @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. @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). @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. |
@ekaitz_zarraga @stikonas Yay, congrats!
Maybe I missed an episode, but why bring another libc into the mix?