Opened 7 months ago

Last modified 7 months ago

#68480 new defect

gcc13 upgrade failure with xcode upgrade to 15 on macOS 13.5.2

Reported by: mu578 (μῦ) Owned by:
Priority: Not set Milestone:
Component: ports Version: 2.8.1
Keywords: ld_classic Cc:
Port: gcc13

Description

macOS    13.5.2 (Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:53 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6020 arm64)
Xcode    15.0
MacPorts 2.8.1
sudo port install gcc13
--->  Computing dependencies for libgcc13
--->  Fetching archive for libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from https://packages.macports.org/libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from http://mirror.fcix.net/macports/packages/libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libgcc13
--->  Building libgcc13
Error: Failed to build libgcc13: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc13/libgcc13/main.log for details.
Error: Problem while installing libgcc13
Error: Unable to execute port: upgrade libgcc failed
:info:build ld: library not found for -ld_classic
:info:build collect2: error: ld returned 1 exit status
:info:build make[3]: *** [libgcc_s.dylib] Error 1

Change History (6)

comment:1 Changed 7 months ago by mu578 (μῦ)

and now since self-update wonky state

sudo port install gcc12
--->  Computing dependencies for libgcc13
--->  Fetching archive for libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from https://packages.macports.org/libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from http://mirror.fcix.net/macports/packages/libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libgcc13
--->  Building libgcc13
Error: Failed to build libgcc13: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc13/libgcc13/main.log for details.
Error: Problem while installing libgcc13
Error: Unable to execute port: upgrade libgcc12 failed

comment:2 Changed 7 months ago by mu578 (μῦ)

sudo port selfupdate
sudo port upgrade outdated
--->  Computing dependencies for libgcc13
--->  Fetching archive for libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from https://packages.macports.org/libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from http://mirror.fcix.net/macports/packages/libgcc13
--->  Attempting to fetch libgcc13-13.2.0_3+stdlib_flag+universal.darwin_22.arm64-x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libgcc13
--->  Building libgcc13
Error: Failed to build libgcc13: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc13/libgcc13/main.log for details.
Error: Problem while installing libgcc13
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.

comment:3 Changed 7 months ago by kencu (Ken)

You didn't include your main.log, but the most likely explanation for your build error is that you updated Xcode to 15, but have not as yet updated the Command Line tools to the matching version.

comment:4 Changed 7 months ago by mu578 (μῦ)

Long story short, updated to Sonoma had to clear all ports and re-install, there is something fishy in that xcode 15 update, was working until I hit that update then trying to upgrade gcc12 to gcc13.

Last edited 7 months ago by mu578 (μῦ) (previous) (diff)

comment:5 Changed 7 months ago by mu578 (μῦ)

no the command tools were updated, I checked all that. Doing it since 20 years.

Last edited 7 months ago by mu578 (μῦ) (previous) (diff)

comment:6 Changed 7 months ago by ryandesign (Ryan Carsten Schmidt)

Please attach the main.log if you'd like us to investigate what went wrong.

Note: See TracTickets for help on using tickets.