Paul Swirhun

Thanks for the detailed response. I do like the `.bazelrc` approach and I'll probably use that to keep it simple (rather than wade into an unfinished Google project like Pigweed)....

Gotcha, I didn’t realize the minus sign was part of the semantics. Yeah, I wasn’t planning on enabling exceptions I was just using that as an example to understand how...

I found that the tools downloaded from commit d3cbe4eff9a63d3dee63067d61096d681daca33b are not compatible with my x86 OSX machine. Specifically, it looks like an assembler/loader compatibility issue I vaguely recall seeing for...

Actually, if I download the files from that link manually, they do run on OSX. The .bzl file which chooses the OS in this project is picking the URL for...

``` >>> bazel info DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1583316607 -0800" DEBUG: Repository rules_cc instantiated at: //WORKSPACE:12:20: in...

My suspicion is that it is something to do with sandboxing on OSX

If I swap git_repository for local_repository, it pulls the correct build tools for OSX. I'm going to chalk this one up to bazel being a large and inscrutable project; and...

> Could there be something else in your workspace that is polluting the `repository_ctx.os.name`? No, there is nothing else in my repo; the only thing in the WORKSPACE file is...

> I will update the readme to match this. That works! What's the difference? Were the instructions just referring to an older commit with broken os name detection? Thank you!

I'm seeing the same limitation trying to install cocotb using poetry on Apple silicon. Weirdly, the pip3 installed version of cocotb works fine on Apple M2 silicon. But, trying to...