I have just upgraded from sonoma to sequoia (15.5) and to xcode 16.3.0, and I
used the macports migration tool to migrate to the new setup. Everything (so
far) seems to be OK except for gcc12. I have gone through the clean-install
cycle four times now with the same failure mode:
:info:build checking whether ln -s works... yes :info:build checking for
aarch64-apple-darwin24-gcc...
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsy
:info:build checking for suffix of object files... configure: error: in
`/opt/local/var/macports/build/_opt_local_var_ma
:info:build configure: error: cannot compute suffix of object files: cannot
compile
:info:build See `config.log' for more details
:info:build make[2]: *** [configure-stage1-target-libgcc] Error 1
:info:build make[2]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org
:info:build make[1]: *** [stage1-bubble] Error 2
:info:build make[1]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org
:info:build make: *** [bootstrap-lean] Error 2
:info:build make: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_ma
:info:build Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macpor
:info:build Exit code: 2
:error:build Failed to build gcc12: command execution failed
:debug:build Error code: CHILDSTATUS 5929 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 10) :debug:build
invoked from within
:debug:build "$procedure $targetname"
:error:build See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarbal
There is an open ticket from two weeks ago that might be this same problem
(#72421) but I'm not versed enough in sorting through failure output logs to
know if they are the same or not. This is the only port install that failed.
So, should I file a new ticket for this?
Jim
Seattle, WA
