Opened 3 years ago

Last modified 3 years ago

#64770 closed defect

rsync @3.2.3_1 build failed on Mojave: clang: error: unable to execute command: Segmentation fault: 11 — at Version 4

Reported by: chillin- Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: mojave catalina Cc:
Port: rsync

Description (last modified by ryandesign (Ryan Carsten Schmidt))

rsync building as dependency of aom
rsync builds without issue on my Mountain Lion box.

Mojave gives this message at failure (which appears simple enough, but I don't understand, e.g. Crash backtrace doesn't exist)

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_rsync/rsync/work/.tmp/simd-checksum-x86_64-fb1268.cpp
clang: note: diagnostic msg: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_rsync/rsync/work/.tmp/simd-checksum-x86_64-fb1268.sh
clang: note: diagnostic msg: Crash backtrace is located in
clang: note: diagnostic msg: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_rsync/rsync/work/.home/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash
clang: note: diagnostic msg: (choose the .crash file that corresponds to your crash)
clang: note: diagnostic msg: 

Change History (5)

Changed 3 years ago by chillin-

Attachment: main.log added

main.log

comment:1 Changed 3 years ago by chillin-

Description: modified (diff)

comment:2 Changed 3 years ago by jmroot (Joshua Root)

Keywords: rsync removed
Milestone: MacPorts Future
Owner: set to ryandesign
Status: newassigned
Summary: Error: Failed to build rsync: command execution failed on Mojaversync @3.2.3_1 build failed on Mojave: clang: error: unable to execute command: Segmentation fault: 11

comment:3 Changed 3 years ago by kencu (Ken)

try cleaning and going again, but if it still fails force a macports clang of your choosing, whatever you have installed should be fine

comment:4 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

rsync builds fine on our buildbot on all macOS versions (10.6 through 12) however I see that you are using Xcode 11.3.1 whereas on macOS 10.14 we use Xcode 10.3. It is conceivable that there is simply a bug in the version of clang that is included with Xcode 11.3.1 that is triggered by building rsync. We can update the port to blacklist that specific version of clang so that MacPorts chooses another version.

Note: See TracTickets for help on using tickets.