[MacPorts] #64770: rsync @3.2.3_1 build failed on Mojave: clang: error: unable to execute command: Segmentation fault: 11

[MacPorts]

#64770: rsync @3.2.3_1 build failed on Mojave: clang: error: unable to execute
command: Segmentation fault: 11
-----------------------+------------------------
  Reporter:  chillin-  |      Owner:  ryandesign
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.7.1
Resolution:            |   Keywords:  mojave
      Port:  rsync     |
-----------------------+------------------------

Old description:

> 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:

New description:

 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:
 }}}

--

Comment (by ryandesign):

 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/64770#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS