Opened 4 hours ago

Closed 99 minutes ago

#70955 closed defect (duplicate)

libgcc14 @14.2.0_2 : Build crashes

Reported by: paulray (Paul Ray) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.10.1
Keywords: Cc:
Port: libgcc14

Description

--->  Computing dependencies for libgcc14
--->  Fetching archive for libgcc14
--->  Attempting to fetch libgcc14-14.2.0_2+stdlib_flag.darwin_23.x86_64.tbz2 from https://packages.macports.org/libgcc14
--->  Attempting to fetch libgcc14-14.2.0_2+stdlib_flag.darwin_23.x86_64.tbz2 from https://mirrors.mit.edu/macports/packages/libgcc14
--->  Attempting to fetch libgcc14-14.2.0_2+stdlib_flag.darwin_23.x86_64.tbz2 from http://bos.us.packages.macports.org/libgcc14
--->  Building libgcc14
Error: Failed to build libgcc14: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc14/libgcc14/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port libgcc14 failed

This is on a MacBook Pro (x86_64) with macOS Sonoma 14.7. Fresh install of Xcode 15.4 with command line tools.

Attachments (1)

main.log (401.4 KB) - added by paulray (Paul Ray) 4 hours ago.
Error log

Download all attachments as: .zip

Change History (4)

Changed 4 hours ago by paulray (Paul Ray)

Attachment: main.log added

Error log

comment:1 Changed 4 hours ago by paulray (Paul Ray)

This has me dead in the water since I can't even compile an earlier libgcc, as it seems that libgcc13 depends on libgcc14 (which is odd).

% sudo port install libgcc13
--->  Computing dependencies for libgcc13
The following dependencies will be installed: 
 libgcc
 libgcc14
Continue? [Y/n]: 

comment:2 Changed 3 hours ago by kencu (Ken)

Version 0, edited 3 hours ago by kencu (Ken) (next)

comment:3 Changed 99 minutes ago by ryandesign (Ryan Carsten Schmidt)

Resolution: duplicate
Status: newclosed

It's not a crash; it's just an error. And yes, it looks like a duplicate of #70750 which will be solved by following Ken's suggestion in comment:2.

Note: See TracTickets for help on using tickets.