https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #16 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- On Tue, 8 Jan 2019, romain.geissler at amadeus dot com wrote: > FYI, what I am following are the Linux From Scratch guidelines, which build > the > initial gcc like this (with both c and C++ support, disabling libstdc++ > build): > http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-pass1.html > Then after building the glibc, they do build the libstdc++ alone like this: > http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-libstdc++.html Those instructions use libc_cv_forced_unwind=yes libc_cv_c_cleanup=yes with glibc, which haven't been needed since my commit e7dbb1bec3be35897acb18aa277807ed276384c5, "Weaken two NPTL configure link tests to compile tests.", March 2012. I advise looking at how glibc's build-many-glibcs.py does things for the modern approach for bootstrapping a cross-compilation toolchain for a target using glibc. (Although some pieces may need adjusting if what you want is a native toolchain using unusual directory arrangements, which some of those LFS instructions seem to suggest.)
