Install on MacOS 12.4 fails

Anki Help
1

System Info:

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro16,1
  Processor Name:	8-Core Intel Core i9
  Processor Speed:	2.4 GHz
  Number of Processors:	1
  Total Number of Cores:	8
  L2 Cache (per Core):	256 KB
  L3 Cache:	16 MB
  Hyper-Threading Technology:	Enabled
  Memory:	32 GB
  System Firmware Version:	1731.120.10.0.0 (iBridge: 19.16.15071.0.0,0)
  OS Loader Version:	540.120.3~6
  Serial Number (system):	C02DR6ZMMD6T
  Hardware UUID:	2E9F15ED-666C-5EBA-9056-BAFEB827CF9A
  Provisioning UDID:	2E9F15ED-666C-5EBA-9056-BAFEB827CF9A
  Activation Lock Status:	Disabled

Steps to reproduce:

  1. clone repo via git and following docs/mac.md…
  2. install xcode via app store and open xcode
  3. curl bazelisk(curl -L link n -o bazel \ && chmod +x bazel . && sudo mv bazel /usr/local/bin)
  4. brew install mpv
  5. brew install lame
  6. install command line tools via xcode-select --install as opening xcode didnt install CLI and errors were thrown in next step
  7. ./tools/runopt (several times until repeated failure with no changes)

Output

$ ./tools/runopt --verbose_failures --sandbox_debug

INFO: Analyzed target //qt:runanki (0 packages loaded, 0 targets configured).

INFO: Found 1 target...

ERROR: /private/var/tmp/_bazel_jason/4c8b2e58bec5ee844904ca7f71062235/external/rules_rust/util/process_wrapper/BUILD.bazel:3:10: Compiling util/process_wrapper/process_wrapper.cc failed: (Exit 1): cc_wrapper.sh failed: error executing command external/local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object -fcolor-diagnostics ... (remaining 31 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox

clang: error: unknown argument: '-fno-canonical-system-headers'

Target //qt:runanki failed to build

Use --verbose_failures to see the command lines of failed build steps.

INFO: Elapsed time: 2.331s, Critical Path: 1.78s

INFO: 17 processes: 17 internal.

FAILED: Build did NOT complete successfully

FAILED: Build did NOT complete successfully
1 Like
2

Try a bazel clean --expunge; something from before the CLI install may be cached.