[MacPorts] #62843: py-cryptography @3.4.7: ports failing to build for MacOS 10.12 and earlier

[MacPorts]

#62843: py-cryptography @3.4.7: ports failing to build for MacOS 10.12 and earlier
------------------------------+----------------------
  Reporter:  mascguy          |      Owner:  stromnov
      Type:  defect           |     Status:  closed
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:
Resolution:  fixed            |   Keywords:
      Port:  py-cryptography  |
------------------------------+----------------------

Comment (by mascguy):

 Looking at the failed builds, it appears that `rustc` is crashing with a
 SIGSEGV:

 {{{
 Building stage1 std artifacts (x86_64-apple-darwin -> x86_64-apple-darwin)
 running:
 "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.52.0-src/build/stage0-x86_64/bin/cargo"
 "build" "--target" "x86_64-apple-darwin" "-Zbinary-dep-depinfo" "-j" "8"
 "-v" "--release" "--frozen" "--features" "panic-unwind backtrace compiler-
 builtins-c" "--manifest-path"
 "/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.52.0-src/library/test/Cargo.toml"
 "--message-format" "json-render-diagnostics"
 error: process didn't exit successfully:
 `/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.52.0-src/build/bootstrap/debug/rustc
 -vV` (exit code: 254)
 --- stdout

 Did not run successfully: signal: 11
 }}}

 The following suggests that it could be an unpatched issue in the LLVM
 toolchain:

 https://github.com/rust-lang/rust/issues/68731

 Are we using the Xcode toolchain, or MacPorts-provided?

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