@microsoft-github-policy-service agree company="Google"

rules_foreign_cc: Build wrapper script location: bazel-out/k8-fastbuild/bin/z3_foreign_cc/wrapper_build_script.sh
rules_foreign_cc: Build script location: bazel-out/k8-fastbuild/bin/z3_foreign_cc/build_script.sh
rules_foreign_cc: Build log location: bazel-out/k8-fastbuild/bin/z3_foreign_cc/Configure.log
rules_foreign_cc: Keeping these below directories for debug, but note that the directories inside a sandbox
rules_foreign_cc: are still cleaned unless you specify the --sandbox_debug Bazel command line flag.
rules_foreign_cc: Build Dir: /home/runner/.cache/bazel/_bazel_runner/565995273ff0f9d48e6a15259e70bb89/sandbox/linux-sandbox/3/execroot/_main/bazel-out/k8-fastbuild/bin/z3.build_tmpdir
rules_foreign_cc: Deps Dir: /home/runner/.cache/bazel/_bazel_runner/565995273ff0f9d48e6a15259e70bb89/sandbox/linux-sandbox/3/execroot/_main/bazel-out/k8-fastbuild/bin/z3.ext_build_deps
Target //:z3 failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 85.123s, Critical Path: 69.89s
INFO: 10 processes: 8 internal, 2 linux-sandbox.
ERROR: Build did NOT complete successfully

I presume this does work from your fork but something got astray with PR environment?

Yeah...let me take another look.

FWIW, these rules worked fine for an older version of Z3. I suspect there were some recent-ish changes to how builds work? I'll convert this PR to a draft until I have things updated.

Just an FYI that I am not actively working on this at this time.