<p dir="auto">Version <code class="notranslate">1.7.1</code> is failing to compile and install via <strong>brew</strong> on an older iMac. The iMac is running <strong>macOS High Sierra</strong>.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="==&gt; Installing deno
==&gt; python build/gen.py
==&gt; ninja -C out
==&gt; cargo install -vv
Last 15 lines from /Users/justin/Library/Logs/Homebrew/deno/03.cargo:
[rusty_v8 0.16.0] See //build/toolchain/mac/BUILD.gn:15:1: whence it was imported.
[rusty_v8 0.16.0] import(&quot;//build/config/mac/mac_sdk.gni&quot;)
[rusty_v8 0.16.0] ^--------------------------------------
[rusty_v8 0.16.0] See //BUILD.gn:4:1: which caused the file to be included.
[rusty_v8 0.16.0] static_library(&quot;rusty_v8&quot;) {
[rusty_v8 0.16.0] ^---------------------------
[rusty_v8 0.16.0] thread 'main' panicked at '
[rusty_v8 0.16.0] command did not execute successfully, got: exit code: 1
[rusty_v8 0.16.0]
[rusty_v8 0.16.0] build script failed, must exit now', /Users/justin/Library/Caches/Homebrew/cargo_cache/registry/src/github.com-1ecc6299db9ec823/cargo_gn-0.0.15/src/lib.rs:203:3
[rusty_v8 0.16.0] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: failed to compile `deno v1.7.1 (/private/tmp/deno-20210204-79091-yndwd1/deno/cli)`, intermediate artifacts can be found at `/private/tmp/deno-20210204-79091-yndwd1/deno/target`

Caused by:
  build failed

Do not report this issue to Homebrew/brew or Homebrew/core!"><pre class="notranslate"><code class="notranslate">==&gt; Installing deno
==&gt; python build/gen.py
==&gt; ninja -C out
==&gt; cargo install -vv
Last 15 lines from /Users/justin/Library/Logs/Homebrew/deno/03.cargo:
[rusty_v8 0.16.0] See //build/toolchain/mac/BUILD.gn:15:1: whence it was imported.
[rusty_v8 0.16.0] import("//build/config/mac/mac_sdk.gni")
[rusty_v8 0.16.0] ^--------------------------------------
[rusty_v8 0.16.0] See //BUILD.gn:4:1: which caused the file to be included.
[rusty_v8 0.16.0] static_library("rusty_v8") {
[rusty_v8 0.16.0] ^---------------------------
[rusty_v8 0.16.0] thread 'main' panicked at '
[rusty_v8 0.16.0] command did not execute successfully, got: exit code: 1
[rusty_v8 0.16.0]
[rusty_v8 0.16.0] build script failed, must exit now', /Users/justin/Library/Caches/Homebrew/cargo_cache/registry/src/github.com-1ecc6299db9ec823/cargo_gn-0.0.15/src/lib.rs:203:3
[rusty_v8 0.16.0] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: failed to compile `deno v1.7.1 (/private/tmp/deno-20210204-79091-yndwd1/deno/cli)`, intermediate artifacts can be found at `/private/tmp/deno-20210204-79091-yndwd1/deno/target`

Caused by:
  build failed

Do not report this issue to Homebrew/brew or Homebrew/core!
</code></pre></div>
<p dir="auto">We struggled with updating deno at Homebrew for a while (cf. <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="766981428" data-permission-text="Title is private" data-url="https://github.com/Homebrew/homebrew-core/issues/66920" data-hovercard-type="pull_request" data-hovercard-url="/Homebrew/homebrew-core/pull/66920/hovercard" href="https://github.com/Homebrew/homebrew-core/pull/66920">Homebrew/homebrew-core#66920</a>) and it seems that part of the reason is that the build is non-deterministic. The exact same build configuration can succeed now and fail (edit: with the same version!) later and vice-versa.</p>
<p dir="auto">This is partly summarized in the table at <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="766981428" data-permission-text="Title is private" data-url="https://github.com/Homebrew/homebrew-core/issues/66920" data-hovercard-type="pull_request" data-hovercard-url="/Homebrew/homebrew-core/pull/66920/hovercard?comment_id=765711570&amp;comment_type=issue_comment" href="https://github.com/Homebrew/homebrew-core/pull/66920#issuecomment-765711570">Homebrew/homebrew-core#66920 (comment)</a>. These are all attempts at building deno 1.7.0.</p>
<p dir="auto">In particular, note that the build configuration is the same between <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/Homebrew/homebrew-core/commit/54c027e24f0ba91816ff906af17efe05d1b5d663/hovercard" href="https://github.com/Homebrew/homebrew-core/commit/54c027e24f0ba91816ff906af17efe05d1b5d663">Homebrew/homebrew-core@<tt>54c027e</tt></a> and <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/Homebrew/homebrew-core/commit/77e4ad870875fb3666c56650622bafc01e7401e2/hovercard" href="https://github.com/Homebrew/homebrew-core/commit/77e4ad870875fb3666c56650622bafc01e7401e2">Homebrew/homebrew-core@<tt>77e4ad8</tt></a> (the first two commits in the table), but the two commits have starkly different build outcomes.</p>
<p dir="auto">The last three commits in that table are also the same, with differing results.</p>