https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122429
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Sam James from comment #2) > On our end with our cross tooling, when bootstrapping cross glibc > configurations, we always build as few target libraries as possible before > we have glibc (libatomic being one we disable), then do another round once > we have glibc. > > The line which added --disable-libatomic for that first round was added long > before me though, so I don't know if libatomic is supposed to require libc > or if someone hit a bug and worked around it a decade ago: > > commit 4d06024dbd6f27ea247fe4db848ac0f01fe7702d > Author: Mike Frysinger <[email protected]> > AuthorDate: Tue May 14 18:46:36 2013 +0000 > Commit: Mike Frysinger <[email protected]> > CommitDate: Tue May 14 18:46:36 2013 +0000 > > disable libatomic when building a stage1 gcc compiler --disable-libatomic is also used in glibc/scripts/build-many-glibcs.py . The only special option I do for glibc is set `CXX=false` before configuring glibc (due to https://sourceware.org/bugzilla/show_bug.cgi?id=24183).
