https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90330
--- Comment #8 from Matt Thompson <matthew.thompson at nasa dot gov> --- (In reply to Iain Sandoe from comment #7) > (In reply to Matt Thompson from comment #6) > > (In reply to Iain Sandoe from comment #5) > > > (In reply to Matt Thompson from comment #4) > > > > Also: I do have all the log files still, so if you'd like anything > > > > grep'ed > > > > in there, let me know. > > > > > > not at this time.. I am trying to figure out what is different about our > > > configurations. > > > > > > --- > > > > > > can you confirm that this was a clean build (including that the target > > > install directory was deleted before the build?) > > > > It was a clean build. I always build out-of-source so it was a new directory > > and I'd never installed GCC 9.1.0 before, so the install directory was new > > as well. > > > > Let me try building again in a new directory with a new install location. Of > > course, being the impressive GCC build, it might be Monday before I can > > report back (it's a work laptop that stays at work). > > OK thanks, as it happens I won't be able to try on Darwin18 before next > Weds, so no hurry. I just tried to rebuild gcc 9.1.0 on my laptop, and I got the same error at the same point in make install. I'll try a few other experiments (remove /usr/local/bin from my path in case brew is causing an issue, though it didn't before). Or should I be using one of my other compilers to build gcc? I have built gcc 8.2.0. Instead of using clang, I could try that...though I'm not sure how. Just pass in CC and CXX to configure?
