libgcc @7.2.0: fatal error: bits/regex_scanner.tcc: No such file or directory

[cjones051073 (Chris Jones)]

Running newly release macOS 10.13. Xcode and CLI tools fully updated.

building libgcc gives

:info:build                  from /opt/local/var/macports/build/_Users_chris_Projects_MacPorts_ports_lang_gcc7/libgcc/work/gcc-7.2.0/libstdc++-v3/include/precompiled/stdc++.h:110:
:info:build /opt/local/var/macports/build/_Users_chris_Projects_MacPorts_ports_lang_gcc7/libgcc/work/build/x86_64-apple-darwin17/libstdc++-v3/include/bits/regex_scanner.h:272:10: fatal error: bits/regex_scanner.tcc: No such file or directory
:info:build  #include <bits/regex_scanner.tcc>

Full log attached.

Port has no maintainer, so not sure who to cc. Looks similar though to ticket:54829

[ryandesign (Ryan Carsten Schmidt)]

Supersedes #54400.

[cjones051073 (Chris Jones)]

There appears to be a non-reproducible nature to the failure. I have run the build a few times now and each time the exact error is slightly different. Its in roughly the same place, and relates to an "bits/XYZ" include, but not exactly the same include each time. For instance

:info:build /opt/local/var/macports/build/_Users_chris_Projects_MacPorts_ports_lang_gcc7/libgcc/work/build/x86_64-apple-darwin17/libstdc++-v3/include/string:41:10: fatal error: bits/allocator.h: No such file or directory
:info:build  #include <bits/allocator.h>
:info:build           ^~~~~~~~~~~~~~~~~~

Could this be an APFS issue (the machine I am using was updated to the new filesystem). I ran checks with the betas version prior to the release, in a VM, and the only difference I can think of is that VM was not using APFS but the old file system...

[ryandesign (Ryan Carsten Schmidt)]

The High Sierra buildbot worker will be set up with HFS+ so we can see if it succeeds there.

[cjones051073 (Chris Jones)]

I have a number of my own VMs, from 10.6 onwards that I use for testing. I am in the process of cloning the macOS 10.12 one to a new 10.13 instance, so I will also be able to test this...