https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #31 from Sergey Fedorov <vital.had at gmail dot com> --- (In reply to Peter Dyballa from comment #27) Did you try a clean build? So far it is not clear to me if anyone of who reported the issue did. And MacPorts builds, by design, are normally tested in clean environment (buildbots never have unrelated ports active). I do the same locally with my builds, at least for anything huge and important (so always for gcc). If unrelated ports or earlier versions of a port which is being built are found, that may lead to unexpected failures. (I am not asking to restart the build from scratch now, that would be a waste of time at the point, it is better to find out if something else fails further.)
