Opened 2 years ago
Last modified 19 months ago
#65850 new defect
libgcc-devel @13-20220911: build fails for macOS 12.6 and Xcode 14
Reported by: | mopihopi | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.2 |
Keywords: | monterey | Cc: | michaelld (Michael Dickens), mascguy (Christopher Nielsen), mike142wood |
Port: | libgcc-devel |
Description
Upgrading libgcc-devel on macOS 12.6 21G115 x86_64 with Xcode 14.0 14A309 fails:
% sudo port upgrade outdated ---> Computing dependencies for libgcc-devel ---> Fetching archive for libgcc-devel ---> Attempting to fetch libgcc-devel-13-20220911_0+stdlib_flag.darwin_21.x86_64.tbz2 from https://packages.macports.org/libgcc-devel ---> Attempting to fetch libgcc-devel-13-20220911_0+stdlib_flag.darwin_21.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libgcc-devel ---> Attempting to fetch libgcc-devel-13-20220911_0+stdlib_flag.darwin_21.x86_64.tbz2 from https://kmq.jp.packages.macports.org/libgcc-devel ---> Fetching distfiles for libgcc-devel ---> Verifying checksums for libgcc-devel ---> Extracting libgcc-devel ---> Configuring libgcc-devel ---> Building libgcc-devel Error: Failed to build libgcc-devel: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
main.log contains this:
:info:build 0 0x10afc3ffa __assert_rtn + 139 :info:build 1 0x10adf728d mach_o::relocatable::Parser<x86_64>::parse(mach_o::relocatable::ParserOptions const&) + 4989 :info:build 2 0x10ade7f8f mach_o::relocatable::Parser<x86_64>::parse(unsigned char const*, unsigned long long, char const*, long, ld::File::Ordinal, mach_o::relocatable::ParserOptions const&) + 207 :info:build 3 0x10ae5e9d4 ld::tool::InputFiles::makeFile(Options::FileInfo const&, bool) + 2036 :info:build 4 0x10ae61fa0 ___ZN2ld4tool10InputFilesC2ER7Options_block_invoke + 48 :info:build 5 0x7ff8182b834a _dispatch_client_callout2 + 8 :info:build 6 0x7ff8182c98f5 _dispatch_apply_invoke + 213 :info:build 7 0x7ff8182b8317 _dispatch_client_callout + 8 :info:build 8 0x7ff8182c7c0c _dispatch_root_queue_drain + 673 :info:build 9 0x7ff8182c825c _dispatch_worker_thread2 + 160 :info:build 10 0x7ff81846bf8a _pthread_wqthread + 256 :info:build A linker snapshot was created at: :info:build /tmp/libstdc++.6.dylib-2022-09-16-123250.ld-snapshot :info:build ld: Assertion failed: (_file->_atomsArrayCount == computedAtomCount && "more atoms allocated than expected"), function parse, file macho_relocatable_file.cpp, line 2061. :info:build collect2: error: ld returned 1 exit status :info:build make[6]: *** [libstdc++.la] Error 1 :info:build make[6]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/x86_64-apple-darwin21/libstdc++-v3/src' :info:build make[5]: *** [all-recursive] Error 1 :info:build make[5]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/x86_64-apple-darwin21/libstdc++-v3/src' :info:build make[4]: *** [all-recursive] Error 1 :info:build make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/x86_64-apple-darwin21/libstdc++-v3' :info:build make[3]: *** [all] Error 2 :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build/x86_64-apple-darwin21/libstdc++-v3' :info:build make[2]: *** [all-stage1-target-libstdc++-v3] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build' :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_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build' :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_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/work/build" && /usr/bin/make -j8 -w bootstrap-lean :info:build Exit code: 2 :error:build Failed to build libgcc-devel: command execution failed :debug:build Error code: CHILDSTATUS 30847 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" :error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details.
Uninstalling gcc-devel and libgcc-devel and then reinstalling with port install produces the same error.
For some reason there is no binary available at https://packages.macports.org/libgcc-devel/, and no macOS 12 build on https://ports.macports.org/port/libgcc-devel/builds/ (either successful or failed).
The error is similar to that in ticket:65573 but with a different port and macOS version.
Attachments (1)
Change History (12)
Changed 2 years ago by mopihopi
Attachment: | libgcc-devel-13-20220911_0-main.log.gz added |
---|
comment:1 follow-up: 7 Changed 2 years ago by mopihopi
comment:2 Changed 2 years ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:3 Changed 2 years ago by mascguy (Christopher Nielsen)
Summary: | libgcc-devel @13-20220911 fails to build with Xcode 14 on macOS 12 → libgcc-devel @13-20220911: build fails for macOS 12 and Xcode 14 |
---|
comment:4 Changed 2 years ago by mascguy (Christopher Nielsen)
Summary: | libgcc-devel @13-20220911: build fails for macOS 12 and Xcode 14 → libgcc-devel @13-20220911: build fails for macOS 12.6 and Xcode 14 |
---|
comment:5 Changed 2 years ago by mascguy (Christopher Nielsen)
Keywords: | monterey added |
---|
comment:6 Changed 2 years ago by michaelld (Michael Dickens)
I've seen this and #65573 for a while ... I did a little code poking ... my best guess is that GCC's build system needs to be tweaked for Darwin 22 ... just a guess. I have not yet contacted Iain yet ... maybe @kencu can do that? Lack of GCC is holding back critical ports when using Xcode 14 or (so I understand) macOS 13-beta + Xcode 14-beta ... like OpenBLAS, NumPy, SciPy, etc. ...
comment:7 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to mopihopi:
apparently there was a large backlog
There was, due to the update of icu to version 71 and the consequent rebuilding of everything that depends on icu. The macOS 12 x86_64 builder also ran out of disk space on one build during that, which caused all subsequent builds to fail, which required some manual cleanup and rescheduling, which I didn't get to right away.
the log file shows that it used an older Xcode (13.2.1) and macOS (12.2.1).
Yes, I have not updated the macOS 12 builders to macOS 12.3 or later because of the removal of /usr/bin/python.
(Oddly there is still no arm64 build even though its buildbot is idle.)
The gcc-devel/libgcc-devel port has for some time been coded to use different versions of software, from different sources, on Intel and Apple Silicon systems. The Apple Silicon part has not yet been updated to this version. It has been customary of late for the Intel and Apple Silicon versions to be updated on different schedules rather than together.
comment:8 Changed 2 years ago by mopihopi
Thanks Ryan! I was curious as to what was going on with the buildbot and that explains it. It appears that it is the older version of Xcode that is causing the buildbot to build libgcc-devel successfully even though it fails locally, so it's good that it was not yet updated.
comment:10 Changed 2 years ago by michaelld (Michael Dickens)
Thanks @kencu for that link. Glad to know Iain & others are on the job. Looking forward to a GCC and/or Apple fix soon-ish!
comment:11 Changed 19 months ago by mike142wood
Cc: | mike142wood added |
---|
The buildbot has now successfully built libgcc-devel @13-20220911 for macOS 12 x86_64 (4 days after the update, so apparently there was a large backlog), although the log file shows that it used an older Xcode (13.2.1) and macOS (12.2.1). (Oddly there is still no arm64 build even though its buildbot is idle.) I was able to install the binary from the Xcode 13.2.1 buildbot for now to work around the Xcode 14.0 build failure.