gcc10 @10.3.0_1+universal fails to build on 10.13

[JohnFHall (John Hall)]

:info:build /opt/local/var/macports/build
/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc10/gcc10/work/build/x86_64-apple-darwin17/libstdc++-v3/include/bits/basic_string.h:48:11: fatal error: string_view: No such file or directory
:info:build    48 | # include <string_view>
:info:build       |           ^~~~~~~~~~~~~
:info:build compilation terminated.}}}

[JohnFHall (John Hall)]

logfile

[kencu (Ken)]

that header should only be called for if you’re building with a c++17 capable compiler that has c++17 mode enabled.

​https://github.com/gcc-mirror/gcc/blob/d25a93742020c2f1efa72d9908406bef6936ab38/libstdc%2B%2B-v3/include/bits/basic_string.h#L47

In which case, the header should be there.

Which part of this is broken?

[metbic]

I think I have similar bug here on yosemite.

sudo port upgrade gcc10
--->  Computing dependencies for gcc10
--->  Fetching archive for gcc10
--->  Attempting to fetch gcc10-10.3.0_1+universal.darwin_14.i386-x86_64.tbz2 from http://packages.macports.org/gcc10
--->  Attempting to fetch gcc10-10.3.0_1+universal.darwin_14.i386-x86_64.tbz2 from http://fra.de.packages.macports.org/gcc10
--->  Attempting to fetch gcc10-10.3.0_1+universal.darwin_14.i386-x86_64.tbz2 from http://nue.de.packages.macports.org/gcc10
--->  Fetching distfiles for gcc10
--->  Verifying checksums for gcc10
--->  Extracting gcc10
--->  Applying patches to gcc10
--->  Configuring gcc10
--->  Building gcc10                                     
Error: Failed to build gcc10: command execution failed   
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc10/gcc10/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Mad-Cat ~> open /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc10/gcc10/main.log

I was thinking, maybe there is something wrong upstream of python39 ​https://trac.macports.org/ticket/64708, so upgraded gcc8, gcc9, both sucessfully, and then gcc10 failed to build.

[metbic]

Or would you suggest I should create a new ticket for this issue?

[cjones051073 (Chris Jones)]

Is this still an issue with the latest gcc10 version ?

[JohnFHall (John Hall)]

Replying to cjones051073:

Is this still an issue with the latest gcc10 version ?

For me I took the cowards way out - I removed all ports using universal and rebuilt all macports.

Bottom line - no idea if uuniversal fails on gcc10. Sorry.