Hi Stefan, Thanks for reaching out!
Stefan <[email protected]> writes: > Hi Maxim! > > I think I solved this already last year without the need for FHS by building > GCC with hard coded paths for all > standard C/C++ files. > > Please search for “a different way to build GCC” in the guix-devel mailing > list or take a look at < > https://git.pub.solar/stefan/embedded-channel>, especially into the file > embedded.scm. It builds a native GCC first > (with all that troubles solved), which is then used to build embedded cross > GCCs. 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]. 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]. Perhaps you'd have some ideas? 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. [0] https://yhetil.org/guix/[email protected]/ [1] https://codeberg.org/apteryx/guix/commit/d87fe691324caec90d1b8df74d09e29d47ea000e [2] https://gist.github.com/apteryks/df92b059fb68559f32951ece5899d30c -- Thanks, Maxim
