Hi Maxim! > Actually, I had recovered the above strategy from [0], > and was trying to migrate our complete toolchain bootstrap to use it, in > this messy exploratory WIP [1].
Oh, nice! I had no clue how to integrate this into the bootstrap chain of Guix. I have the overall impression that the current bootstrap path is not straight forward and too fragil with old package versions inheriting from newer ones. So I started the “integration” from the other far end with bootar. I meanwhile found fixes and improvements to Mes to build the upstream TCC directly (yes, Ekaitz!) and a shorter bootstrap path up to static GCC 15 with static musl. I’m lacking time, so this is not yet pushed into my repository. But hopefully in two weeks. > Unfortunately I'm stuck on building libstdc++ with hard to understand > configure-time errors, and not sure how to proceed from there. The > config.log left from the failed configure of libstdc++ reads [2]. I’ll take a look at it in a week. > Perhaps you'd have some ideas? I think it could instead be possible to just extract libstdc++ from the GCC package, instead of building it standalone. I’m not sure, I guess only clang requires lidstdc++. But we build clang with GCC anyway. So I see no loss at all, if libstdc++ is not build on its own. > We should team up an get this done! This > is a long standing issue in Guix that comes back to haunt us every now > and then. Yes, please! Unfortunately I’m currently away from home. My next bootstrap hurdle is the current glibc, which requires python, and I don’t know yet about all the dependencies of python. Bye Stefan
