https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90330
--- Comment #13 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Matt Thompson from comment #12) > (In reply to Iain Sandoe from comment #11) > > (In reply to Matt Thompson from comment #10) > > > (In reply to Iain Sandoe from comment #9) > > > > (In reply to Matt Thompson from comment #8) > > > > yes, and/or make sure that the GCC toolchain bin dir is before the > > > > system > > > > ones in your path. > > > > > > I'll try this as well as soon as I can (I can maybe manage make -j4 on > > > this > > > laptop, so builds aren't quick!). Do I need to pass FC as well? Or does > > > the > > > gcc build with fortran not care? > > > > Fortran is built with the C++ compiler, but I'd put the GCC bin dir in the > > path first - and then you will be able to do the DYLD_** commands using the > > bootstrap compiler tools to install. > > Well, 9.1.0 built just fine with 8.2.0 loaded in my environment. This seems > to point to clang, which, well, doesn't surprise me as clang and I have had > a difficult life together, but then again clang built 5.4.0 up to 8.2.0 just > fine for me. > > I'm ran a 'make check' and got: > > Fixed: time.h > Fixed: tinfo.h > Fixed: types/vxTypesBase.h > Fixed: unistd.h > Newly fixed header: sys/ucred.h > > There were fixinclude test FAILURES > make[2]: *** [Makefile:177: check] Error 1 > make[2]: Leaving directory > '/Users/mathomp4/src/GCC/gcc-9.1.0-BUILD-820loaded/fixincludes' > make[1]: *** [Makefile:3829: check-fixincludes] Error 2 > make[1]: Leaving directory > '/Users/mathomp4/src/GCC/gcc-9.1.0-BUILD-820loaded' > make: *** [Makefile:2358: do-check] Error 2 do you have runtest and/or autopen in your path - if not then you won't get any results - you probably need to append the path(s) for home-brew to the end of your PATH. > > So...huh. Not sure what to do there. Still, fortune favors the bold/naive > and I'll continue work with this 9.1.0 and try to build my MPI stack, etc. > and see how it handles our model. OK, so I am happy to work with you to get this working for your environment. GCC should build and install with clang as the bootstrap compiler. For that, I think maybe we should just pick up a direct email discussion and close this PR (since it seems something specific to your setup). NOTE: toolchain "vendors" (including macports et. al.) would normally not support anything that they don't test so the advice would be either: a) build in macports/fink/homebrew unchanged or b) configure and build stand-alone with full control over the environment. Personally, I do (b) because I want the toolchain to work independent of any dependencies from the distributions. Many people who are just building a toolchain for their own use can do (a).
