Opened 2 weeks ago

Last modified 2 weeks ago

#71130 new defect

segfault building gd2 on Mac OS Sequoia — at Initial Version

Reported by: RivetBenoit (Benoit Rivet) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: gd2

Description

Trying to install gd2 on Mac OS Sequoia on a mid 2012 Macbook Pro (using Open Core Legacy Patcher to install Mac OS Sequoia) fails due to segfault, as shown line 2148 on the attached log file.

:info:build clang: error: unable to execute command: Segmentation fault: 11
:info:build clang: error: clang frontend command failed due to signal (use -v to see invocation)
:info:build Apple clang version 16.0.0 (clang-1600.0.26.3)
:info:build Target: x86_64-apple-darwin24.0.0
:info:build Thread model: posix
:info:build InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Lines 2163 to 2165 claim there is a crash backtrace file, but I could not find any on the location indicated in main.log.

:info:build clang: note: diagnostic msg: Crash backtrace is located in
:info:build clang: note: diagnostic msg: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gd2/gd2/work/.home/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash
:info:build clang: note: diagnostic msg: (choose the .crash file that corresponds to your crash)

Files attached : main.log, gd_filter-a6bcd3.c and gd_filter-a6bcd3.sh (see lines 2161 and 2162 of main.log).

I tried sudo port clean gd2 and sudo port -f selfupdate as mentionned in https://trac.macports.org/ticket/71015 before attempting a new install of gd2 but this did not solve the problem. Strangely enough, gd2 installed fine on a 2012 MacMini with Mac OS Sequoia.

Change History (3)

Changed 2 weeks ago by RivetBenoit (Benoit Rivet)

Attachment: main.log added

Changed 2 weeks ago by RivetBenoit (Benoit Rivet)

Attachment: gd_filter-a6bcd3.c added

Changed 2 weeks ago by RivetBenoit (Benoit Rivet)

Attachment: gd_filter-a6bcd3.sh added
Note: See TracTickets for help on using tickets.