go fails to upgrade to @1.17.10 for x86_64 on 10.6.8

[barracuda156]

:info:build # cmd/vet
:info:build ld: warning: can't parse dwarf compilation unit info in /opt/x86_64/var/macports/build/_opt_x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/work/.tmp/go-link-1557929151/go.o
:info:build go tool dist: FAILED: /opt/x86_64/var/macports/build/_opt_x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/work/go/pkg/tool/darwin_amd64/go_bootstrap install -gcflags=all= -ldflags=all="-extldflags=-Wl,-headerpad_max_install_names -L/opt/x86_64/lib -lMacportsLegacySupport" -v std cmd: exit status 2
:info:build rm -r /opt/x86_64/var/macports/build/_opt_x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/work/go/pkg/bootstrap
:info:build rm -r /opt/x86_64/var/macports/build/_opt_x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/work/go/pkg/obj/go-build
:info:build rm -rf /opt/x86_64/var/macports/build/_opt_x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/work/.tmp/go-tool-dist-190051773
:info:build rm -r /opt/x86_64/var/macports/build/_opt_x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/work/.tmp/go-tool-dist-190051773
:info:build Command failed:  cd "/opt/x86_64/var/macports/build/_opt_x86_64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_go/go/work/go/src" && ./make.bash -v=3 
:info:build Exit code: 2
:error:build Failed to build go: command execution failed
:debug:build Error code: CHILDSTATUS 53104 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"

[barracuda156]

The previous version built just fine:

macmini:bin svacchanda$ ./port -v installed go
The following ports are currently installed:
  go @1.17.9_0 (active) requested_variants='' platform='darwin 10' archs='x86_64' date='2022-05-11T00:33:35+0800'

[mascguy (Christopher Nielsen)]

Given what folks have been able to accomplish with our other toolchain components - particularly rust, for example - is this not fixable...?

[catap (Kirill A. Korinsky)]

Christopher it does.

I do have unfinished work, but lack of time blocking me :)

[mascguy (Christopher Nielsen)]

@macportsraf, this ticket supersedes issue:52506

[mascguy (Christopher Nielsen)]

Replying to catap:

Christopher it does.

I do have unfinished work, but lack of time blocking me :)

No worries Kirill. And glad to hear that a fix is on the horizon!

[barracuda156]

Replying to mascguy:

Given what folks have been able to accomplish with our other toolchain components - particularly rust, for example - is this not fixable...?

Do you know by chance if anyone tried fixing Go-1.4 for PPC? It is supposed to be bootstrappable from C sources, but in fact source code lacks necessary components (adding arch definitions isn’t enough). Should be still feasible, just time-consuming. Then, 1.9 has ppc32 support in one of its forks, I believe, but to build that we need some functional Go already.

[barracuda156]

Replying to mascguy:

Replying to catap:

Christopher it does.

I do have unfinished work, but lack of time blocking me :)

No worries Kirill. And glad to hear that a fix is on the horizon!

I think something got broken elsewhere on Intel in Macports. I cannot build 1.17.9 now on 10.6.8 x86_64, while it worked before.

Either compiler choice changed or cctools, or ld64 (or legacysupport, possibly?). It is not Go as such.

UPD. Or the procedure. I tried to build 1.17.9 now from the current portfile (replacing version). Let me try to revert to the old one. UPD2. Well, it is not that trivial to revert anything, since even distfiles for cctools and ld64 are gone. And there were changes to PGs used.

It could be a solution to turn off debug symbols in Go for failing systems, like it is done for iOS. Perhaps.