arm-none-eabi-gcc @5.4.0_3 fails to build

[tcwan (TC Wan)]

arm-none-eabi-gcc fails to build on latest macOS 10.13 High Sierra

[tcwan (TC Wan)]

Build log for arm-none-eabi-gcc 5.4.0_3

[notthetup (Chinmay Pendharkar)]

From the logs, this seems to be an issue? Did OSX changed their cli syntax in High Sierra which is causing this??

:info:build make[1]: *** [all-gcc] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/build'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/build'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/build" && /usr/bin/make -j4 -w all 
:info:build Exit code: 2
:error:build Failed to build arm-none-eabi-gcc: command execution failed
:debug:build Error code: CHILDSTATUS 9529 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"

[notthetup (Chinmay Pendharkar)]

Looking again carefully there is another error.

:info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2: error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean simply 'fancy_abort'?
:info:build         _VSTD::abort();
:info:build         ^~~~~~~

Replying to notthetup:

From the logs, this seems to be an issue? Did OSX changed their cli syntax in High Sierra which is causing this??

:info:build make[1]: *** [all-gcc] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/build'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/build'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-none-eabi-gcc/arm-none-eabi-gcc/work/build" && /usr/bin/make -j4 -w all 
:info:build Exit code: 2
:error:build Failed to build arm-none-eabi-gcc: command execution failed
:debug:build Error code: CHILDSTATUS 9529 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"

[tcwan (TC Wan)]

Replying to notthetup:

I don't think it is a simple problem with High Sierra cli. There seems to be some other compiler related issue involved here. Unfortunately I don't know where to start looking since the syntax error is quite innocuous.

Is MacPorts attempting to build arm-none-eabi-gcc using Clang and its C++ libraries?? Maybe it needs to use g++ libraries instead.

Looking again carefully there is another error.

:info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/functional:1398:2: error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean simply 'fancy_abort'?
:info:build         _VSTD::abort();
:info:build         ^~~~~~~

[kencu (Ken)]

The specified error is an error in building gcc5 that has been fixed in gcc 5.5.

I have fixed some simple gcc build errors before, and so I took 20 minutes to look into this, but it's going to be what looks like a lot more work than that to straighten it all out. Just adding in the fix to gcc 5.4's gcc/system.h did not allow the port to build for me.

It looks to me like the whole crossgcc group of ports and the supporting PortGroup file is going to need to be looked at and updated.

/opt/macports-ports/_resources/port1.0/group/crossgcc-1.0.tcl

[tcwan (TC Wan)]

I guess this ticket can be closed since arm-none-eabi-gcc-7.3 has been released.