https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858
Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |--- Status|RESOLVED |UNCONFIRMED --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Matthew Krupcale from comment #6) > (In reply to Andrew Pinski from comment #5) > > Best way to support this really is to build a 4.8 cross compiler and then > > build a canandian cross GCC 4.8 and then bootstrap a 4.8.x using that newly > > build canandian cross compiler. > > I'm not sure I follow exactly because I wasn't trying to build a cross > compiler, although I suppose once you have a GCC 4.8 compiler built (cross > or not), you wouldn't have a problem building 4.8.x with it in theory. But > the problem is building that initial GCC 4.8 (cross or not) with the newer > GCC version. You misunderstood. Building a cross compiler and a canadian cross is so the new 4.8 compiler is NOT exposing to the bootstrap issue you mentioned. 4.8 and 8.x are no longer maintained so fixing those are out of the question. stage1 of gcc does not require the LD_LIBRARY_PATH to be set at all and stage 2 and 3 will use -static-libstdc++. Of course LD_LIBRARY_PATH shouldn't be needed these days.